← previous blocknext block →recent activity
Analyzing
Block #95,746,467
34 transactions · 33 stateful · 2026-08-13 22:09:04 UTC
Parallelism
53/100
Blocked
70%
Avg conflicts / tx
2.85
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #95,746,467 · 34 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w18w29w310w211w412w513w614w715w819w922w1225w1026w1128w1231w1332w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xacd1b162…bee6
0x34b655…2a6f
10 touches
10 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
10 touches
10 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
10 touches
10 conflicts
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
28 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity