← previous blocknext block →recent activity
Analyzing
Block #95,154,194
19 transactions · 16 stateful · 2026-08-11 20:15:25 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,154,194 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w28w39w410w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd20b4e3…e8d3
0x34b655…2a6f
10 touches
10 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0xc0164b20…4db5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
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
10 conflicts on slot 0xbd20b4e389…71e8d3
Audit this contract →
← previous block·next block →recent activity