← previous blocknext block →recent activity
Analyzing
Block #95,279,031
11 transactions · 9 stateful · 2026-08-12 06:52:12 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,279,031 · 11 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce06a0f7…efef
0x34b655…2a6f
4 touches
1 conflict
0x2628fbf6…2e46
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x5c1e4658…3669
0x34b655…2a6f
3 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
2 touches
0 conflicts
0xc13e1d5c…62c6
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 0xce06a0f7c4…61efef
Audit this contract →
← previous block·next block →recent activity