#block
2 APIs con questa etichetta
Block Time API
Konvertieren Sie einen Zeitstempel oder ein Datum in die Blocknummer, die zu diesem Zeitpunkt auf einer von über 100 Blockchains live war, schlüssellos. On-Chain-Analysten, Indexierer und Dashboards benötigen ständig „Welcher Block war Chain X zum Zeitpunkt T“, um den historischen Zustand abzufragen, und „Welche Blöcke decken dieses Zeitfenster ab“, um einen Zeitraum zu scannen. Diese API beantwortet beides – für einen einzelnen Moment und für einen Datumsbereich (Rückgabe des Start- und Endblocks sowie der Blockanzahl und der durchschnittlichen Blockzeit). Live, nichts wird gespeichert. Die Timestamp-to-Block-Ebene für EVM- und Nicht-EVM-Chains gleichermaßen. Unterstützt durch die offene DeFiLlama Coins API.
api.oanor.com/blocktime-api
Masonry Estimating API
Masonry estimating maths as an API, computed locally and deterministically — the brick, block and mortar counts a bricklayer, builder or estimator works to. The brick endpoint computes how many bricks a wall needs from its area (or length × height in feet): bricks per square foot = 144 / ((brick length + joint) × (brick height + joint)), so a standard modular brick with a 3/8-inch mortar joint works out to the well-known 6.86 bricks per square foot — a 100 ft² wall is 686 bricks, plus a waste allowance and the mortar bags (about 7 per 1000 bricks). The block endpoint does the same for concrete masonry units: a standard 16×8-inch CMU with a 3/8-inch joint is 1.125 blocks per square foot, with roughly 2.5 mortar bags per 100 blocks. Both endpoints take custom unit face dimensions and joint thickness, add a configurable waste percentage and round up to whole units. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, masonry-contractor, building-supply and home-improvement app developers, takeoff and material-estimating tools, and trade calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches and square feet). Live, nothing stored. 2 compute endpoints. This is brick/block and mortar estimating; for poured-concrete volume use a concrete API and for drywall use a drywall API.
api.oanor.com/masonry-api