← previous blocknext block →recent activity
Analyzing
Block #96,494,220
11 transactions · 8 stateful · 2026-08-16 12:50:32 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,494,220 · 11 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
5w06w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf59d5c4…7b64
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0xfb657a90…637f
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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 0xcf59d5c48d…e77b64
Audit this contract →
← previous block·next block →recent activity