← previous blocknext block →recent activity
Analyzing
Block #96,638,708
12 transactions · 11 stateful · 2026-08-17 00:57:33 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,638,708 · 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
2w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9efbd42c…c1bb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 conflicts
0x4044ba53…1a0f
0x34b655…2a6f
8 touches
6 conflicts
0x640c4fb2…044a
0x34b655…2a6f
7 touches
6 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0xa399fba3…eeb4
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
6 conflicts on slot 0x9efbd42cc6…4dc1bb
Audit this contract →
← previous block·next block →recent activity