← previous blocknext block →recent activity
Analyzing
Block #92,057,808
21 transactions · 19 stateful · 2026-08-01 00:21:40 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,057,808 · 21 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
4w07w08w19w210w311w412w113w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xc7533437…443e
0x7b9256…1fb2
8 touches
6 conflicts
0xc7533437…443f
0x7b9256…1fb2
8 touches
6 conflicts
0xc7533437…4442
0x7b9256…1fb2
8 touches
6 conflicts
0x7ef5f764…1896
0x7b9256…1fb2
8 touches
6 conflicts
0x7ef5f764…1897
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
15 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity