← previous blocknext block →recent activity
Analyzing
Block #95,414,896
24 transactions · 23 stateful · 2026-08-12 18:20:04 UTC
Parallelism
54/100
Blocked
52%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #95,414,896 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w69w711w813w517w919w123w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xf4f18a3d…61d4
0x34b655…2a6f
5 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
5 touches
3 conflicts
0xc6b1d981…1be2
0xa6afd3…d132
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
21 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity