← previous blocknext block →recent activity
Analyzing
Block #95,719,510
24 transactions · 21 stateful · 2026-08-13 19:53:29 UTC
Parallelism
92/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,719,510 · 24 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
2w03w19w013w116w017w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xc61d8a1d…18fd
0x34b655…2a6f
4 touches
1 conflict
0x3a3c1ed9…9dd5
0x34b655…2a6f
2 touches
0 conflicts
0x3f3796ab…a67c
0x34b655…2a6f
2 touches
0 conflicts
0x403b061b…9f34
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 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity