← previous blocknext block →recent activity
Analyzing
Block #95,405,837
27 transactions · 23 stateful · 2026-08-12 17:34:11 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,405,837 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w17w28w09w010w011w112w213w314w018w119w321w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x89ad7378…b17f
0xd32edf…ff58
7 touches
6 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
6 touches
3 conflicts
0x63f5c02f…6853
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x850662…52d0
6 touches
3 conflicts
0x00000000…0004
0x850662…52d0
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x51360289…9b26
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
6 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity