← previous blocknext block →recent activity
Analyzing
Block #89,277,673
14 transactions · 13 stateful · 2026-07-21 20:22:22 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,277,673 · 14 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
1w02w16w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f637473…d7bd
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x20497f5e…c503
0x34b655…2a6f
6 touches
3 conflicts
0x6d6c7e13…e045
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd742cf7d…02d7
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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 0x5f637473d7…22d7bd
Audit this contract →
← previous block·next block →recent activity