← previous blocknext block →recent activity

Analyzing

Block #92,370,677

49 transactions · 36 stateful · 2026-08-02 02:35:10 UTC

Parallelism

80/100

Blocked

72%

Avg conflicts / tx

1.96

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,370,677  ·  49 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0xa6afd3…d132

16 touches
28 conflicts

0x00000000…0002

0x91855e…ac7e

16 touches
28 conflicts

0x1a287886…0266

0xa6afd3…d132

14 touches
21 conflicts

0xdc818321…be7e

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…002a

0x1b6862…e19c

12 touches
15 conflicts

0x11998eac…f9a1

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-WETH/USDC

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity