← previous blocknext block →recent activity
Analyzing
Block #89,747,358
26 transactions · 21 stateful · 2026-07-23 22:13:21 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,747,358 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w29w010w111w212w316w017w118w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0xada5476f…d55b
0x0a2fbf…29b1
6 touches
3 conflicts
0xada5476f…d55c
0x0a2fbf…29b1
6 touches
3 conflicts
0xada5476f…d55f
0x0a2fbf…29b1
6 touches
3 conflicts
0xc55314cc…a697
0x0a2fbf…29b1
6 touches
3 conflicts
0xc55314cc…a698
0x0a2fbf…29b1
6 touches
3 conflicts
0xe8d58d34…426d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity