← previous blocknext block →recent activity
Analyzing
Block #95,594,671
17 transactions · 15 stateful · 2026-08-13 09:24:30 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,594,671 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w410w411w112w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x0e3ff280…1207
0xa6afd3…d132
4 touches
1 conflict
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity