← previous blocknext block →recent activity
Analyzing
Block #95,393,703
26 transactions · 22 stateful · 2026-08-12 16:32:49 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,393,703 · 26 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
1w05w16w27w08w19w210w311w413w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0xcff4dd72…06df
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc431dcb4…ebed
0x34b655…2a6f
5 touches
3 conflicts
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
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
10 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity