← previous blocknext block →recent activity
Analyzing
Block #95,153,109
15 transactions · 14 stateful · 2026-08-11 20:09:58 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,153,109 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w19w212w313w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0xbe9baf16…df37
0x34b655…2a6f
6 touches
3 conflicts
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x0725ad1d…a03f
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3de86e79…4d3d
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity