← previous blocknext block →recent activity
Analyzing
Block #95,204,624
20 transactions · 19 stateful · 2026-08-12 00:29:04 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,204,624 · 20 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
2w03w04w16w27w38w010w311w112w013w414w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26784e10…ca1f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x992fec28…420d
0x34b655…2a6f
4 touches
1 conflict
0xb19c04c4…0b3e
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
15 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity