← previous blocknext block →recent activity
Analyzing
Block #95,074,344
51 transactions · 46 stateful · 2026-08-11 13:33:44 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
3
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #95,074,344 · 51 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w010w011w112w113w214w215w316w318w526w427w528w632w635w741w1243w244w345w446w349w1350w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x8eef368f…aa21
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity