← previous blocknext block →recent activity
Analyzing
Block #96,602,618
10 transactions · 9 stateful · 2026-08-16 21:56:02 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,602,618 · 10 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
1w02w13w04w15w26w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea6a484b…20e5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x928a50b6…222b
0x34b655…2a6f
6 touches
3 conflicts
0xdba3b90b…02bd
0x34b655…2a6f
4 touches
1 conflict
0xd76a03c0…e690
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x8c381258…46d0
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 0xea6a484b4c…e320e5
Audit this contract →
← previous block·next block →recent activity