← previous blocknext block →recent activity
Analyzing
Block #89,413,112
19 transactions · 16 stateful · 2026-07-22 11:27:41 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,413,112 · 19 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
1w02w16w07w18w211w012w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cf3be9e…3276
0x34b655…2a6f
6 touches
3 conflicts
0xf0aaad90…2697
0x34b655…2a6f
6 touches
3 conflicts
0x9ee338ef…ab21
0x34b655…2a6f
4 touches
2 conflicts
0x08fcf12d…5a3f
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x45877cba…0b50
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a308232…abc8
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 0x0cf3be9ea2…783276
Audit this contract →
← previous block·next block →recent activity