← previous blocknext block →recent activity
Analyzing
Block #95,078,601
10 transactions · 9 stateful · 2026-08-11 13:55:09 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,078,601 · 10 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
2w03w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0xc5a847e4…8333
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
2 touches
0 conflicts
0x6771eae2…7014
0x34b655…2a6f
2 touches
0 conflicts
0xb4527790…c282
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 0xac3e4969cf…1739e9
Audit this contract →
← previous block·next block →recent activity