← previous blocknext block →recent activity
Analyzing
Block #96,369,027
14 transactions · 12 stateful · 2026-08-16 02:20:52 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,369,027 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w28w39w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82dd99dd…a361
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x82dd99ddd8…afa361
Audit this contract →
← previous block·next block →recent activity