← previous blocknext block →recent activity
Analyzing
Block #95,032,668
20 transactions · 20 stateful · 2026-08-11 10:03:20 UTC
Parallelism
60/100
Blocked
35%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,032,668 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w210w311w412w513w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x7c200611…8d6b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe84ca9a7…b041
0x34b655…2a6f
10 touches
10 conflicts
0x772ab420…c2f6
0x34b655…2a6f
8 touches
6 conflicts
0xd800e635…b1d7
0x34b655…2a6f
8 touches
6 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity