← previous blocknext block →recent activity
Analyzing
Block #89,581,086
24 transactions · 19 stateful · 2026-07-23 06:09:46 UTC
Parallelism
92/100
Blocked
26%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,581,086 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w114w115w016w121w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x593e0d07…64bc
0x0a2fbf…29b1
4 touches
1 conflict
0x593e0d07…64bd
0x0a2fbf…29b1
4 touches
1 conflict
0xf5b8399d…a3c4
0x0a2fbf…29b1
4 touches
1 conflict
0xf5b8399d…a3c5
0x0a2fbf…29b1
4 touches
1 conflict
0xf5b8399d…a3c8
0x0a2fbf…29b1
4 touches
1 conflict
0x14c4e3ca…edd9
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity