← previous blocknext block →recent activity
Analyzing
Block #92,072,761
13 transactions · 11 stateful · 2026-08-01 01:36:53 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,072,761 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfa382ba…52b2
0x7b9256…1fb2
10 touches
10 conflicts
0xcfa382ba…52b3
0x7b9256…1fb2
10 touches
10 conflicts
0xdc208a5b…6b5f
0x7b9256…1fb2
10 touches
10 conflicts
0xdc208a5b…6b60
0x7b9256…1fb2
10 touches
10 conflicts
0xdc208a5b…6b63
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 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
10 conflicts on slot 0xcfa382bad5…4052b2
Audit this contract →
← previous block·next block →recent activity