← previous blocknext block →recent activity
Analyzing
Block #96,490,608
10 transactions · 9 stateful · 2026-08-16 12:32:22 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,490,608 · 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
1w02w13w14w25w36w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x123650c5…8859
0x34b655…2a6f
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x5c5238c6…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
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 0x123650c53c…b78859
Audit this contract →
← previous block·next block →recent activity