← previous blocknext block →recent activity
Analyzing
Block #96,436,589
9 transactions · 7 stateful · 2026-08-16 08:00:39 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,436,589 · 9 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x833f3561…bfd0
0x34b655…2a6f
2 touches
0 conflicts
0x921a58d1…db22
0x34b655…2a6f
2 touches
0 conflicts
0xda95d80c…a64c
0x34b655…2a6f
2 touches
0 conflicts
0x0cfb5d79…7ccb
0xb754ba…508d
2 touches
0 conflicts
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 0x9b2d3bee9d…d68eec
Audit this contract →
← previous block·next block →recent activity