← previous blocknext block →recent activity
Analyzing
Block #89,572,287
12 transactions · 11 stateful · 2026-07-23 05:11:07 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,572,287 · 12 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
2w03w05w06w17w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c15f714…46ab
0x34b655…2a6f
4 touches
1 conflict
0x10981d9e…6ebc
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d4
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0x2cd98078…527c
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
1 conflict on slot 0x0c15f714cb…5246ab
Audit this contract →
← previous block·next block →recent activity