← previous blocknext block →recent activity

Analyzing

Block #91,958,226

18 transactions · 16 stateful · 2026-07-31 16:00:49 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,958,226  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x43fab434…896f

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3de775b2…319b

0xa6afd3…d132

6 touches
3 conflicts

0xca2926e0…61b5

0x34b655…2a6f

4 touches
1 conflict

0x04717fc0…1cf7

0x34b655…2a6f

4 touches
1 conflict

0x2029b74e…c206

0x34b655…2a6f

4 touches
1 conflict

0x6e6b8ec7…2197

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x43fab43468…d0896f

← previous block·next block →recent activity