← previous blocknext block →recent activity
Analyzing
Block #95,075,127
47 transactions · 45 stateful · 2026-08-11 13:37:41 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
2.89
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #95,075,127 · 47 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
2w03w14w05w06w17w18w29w310w311w412w515w619w720w824w926w1027w1128w1229w1330w1433w234w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x61681cb3…aa6d
0x34b655…2a6f
18 touches
36 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
18 touches
36 conflicts
0x34ab11f0…f529
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6426
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x734ee320…caae
0x34b655…2a6f
14 touches
21 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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity