← previous blocknext block →recent activity
Analyzing
Block #95,654,611
17 transactions · 16 stateful · 2026-08-13 14:26:00 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,654,611 · 17 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
2w03w04w15w110w212w013w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26e32e90…8827
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x1b1b086a…4542
0x34b655…2a6f
6 touches
3 conflicts
0xfb67be15…a190
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x5e6a725f…3b35
0x34b655…2a6f
4 touches
1 conflict
0xb825b472…1315
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 0x26e32e90f9…688827
Audit this contract →
← previous block·next block →recent activity