← previous blocknext block →recent activity
Analyzing
Block #89,404,610
12 transactions · 12 stateful · 2026-07-22 10:30:51 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,404,610 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb26fce3e…f47f
0x34b655…2a6f
4 touches
1 conflict
0xeb403811…08ce
0x34b655…2a6f
4 touches
1 conflict
0xb652c396…b8fa
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0bf3e6e6…a411
0x34b655…2a6f
4 touches
1 conflict
0x26c87567…04bb
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 0xb26fce3e2d…63f47f
Audit this contract →
← previous block·next block →recent activity