← previous blocknext block →recent activity
Analyzing
Block #92,162,142
14 transactions · 13 stateful · 2026-08-01 09:06:25 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,162,142 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w210w011w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6ecbee4…9d35
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x14049d6c…bbe6
0x7b9256…1fb2
6 touches
3 conflicts
0x14049d6c…bbe7
0x7b9256…1fb2
6 touches
3 conflicts
0xa6ecbee4…9d38
0x7b9256…1fb2
6 touches
3 conflicts
0xa6ecbee4…9d34
0x7b9256…1fb2
6 touches
3 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
3 conflicts on slot 0xa6ecbee4b8…ec9d35
Audit this contract →
← previous block·next block →recent activity