← previous blocknext block →recent activity
Analyzing
Block #96,544,292
9 transactions · 7 stateful · 2026-08-16 17:02:40 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,544,292 · 9 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
2w03w14w25w36w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x881782b6…c51a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x082e2487…91bb
0x968279…9342
4 touches
1 conflict
0x0431e51f…6f91
0x34b655…2a6f
4 touches
1 conflict
0x201d7cf1…f7f2
0x34b655…2a6f
4 touches
1 conflict
0x018ff2f4…e256
0x968279…9342
4 touches
1 conflict
0x018ff2f4…e257
0x968279…9342
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 0x881782b64f…84c51a
Audit this contract →
← previous block·next block →recent activity