← previous blocknext block →recent activity
Analyzing
Block #89,784,889
20 transactions · 19 stateful · 2026-07-24 01:22:51 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,784,889 · 20 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
2w03w15w06w18w09w110w211w116w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06b5ee9d…471b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7a2fc410…c088
0x34b655…2a6f
6 touches
3 conflicts
0xbd6941a1…6281
0x34b655…2a6f
6 touches
3 conflicts
0x4a7aa058…f12e
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b44
0x34b655…2a6f
4 touches
1 conflict
0x6474161a…6a37
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: Perpl
3 conflicts on slot 0x06b5ee9d4a…71471b
Audit this contract →
← previous block·next block →recent activity