← previous blocknext block →recent activity
Analyzing
Block #96,595,534
7 transactions · 5 stateful · 2026-08-16 21:20:24 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,595,534 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x004ab53c…043e
0x34b655…2a6f
2 touches
0 conflicts
0x0342cc6e…beda
0x34b655…2a6f
2 touches
0 conflicts
0x0419260c…d009
0x34b655…2a6f
2 touches
0 conflicts
0x1e927cee…d3a1
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
0x34b655…2a6f
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 0x0cc657206f…8a396c
Audit this contract →
← previous block·next block →recent activity