← previous blocknext block →recent activity
Analyzing
Block #95,127,689
21 transactions · 21 stateful · 2026-08-11 18:02:06 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,127,689 · 21 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
2w03w14w05w16w08w210w111w213w014w315w116w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
10 conflicts on slot 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity