← previous blocknext block →recent activity
Analyzing
Block #96,353,611
12 transactions · 11 stateful · 2026-08-16 01:03:20 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,353,611 · 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
6w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7f67d8a…1412
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x713ba679…f953
0x34b655…2a6f
4 touches
1 conflict
0xb8746edd…bc38
0x34b655…2a6f
4 touches
1 conflict
0x26607bc2…7fd6
0x34b655…2a6f
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
2 touches
0 conflicts
0xbb97db90…4c93
0xc8689a…ee79
2 touches
0 conflicts
0x7628deed…422d
0xd42a27…01c7
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
6 conflicts on slot 0xf7f67d8a8f…171412
Audit this contract →
← previous block·next block →recent activity