← previous blocknext block →recent activity
Analyzing
Block #96,282,262
11 transactions · 9 stateful · 2026-08-15 19:04:29 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,282,262 · 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
2w03w17w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0x3a7f96df…f31e
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x53a854a3…8db8
0x34b655…2a6f
4 touches
1 conflict
0x578347c5…cb6e
0x34b655…2a6f
4 touches
1 conflict
0x5f689f7f…d18e
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x83708836…56ef
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
1 conflict on slot 0xc550cc4849…c9815e
Audit this contract →
← previous block·next block →recent activity