← previous blocknext block →recent activity
Analyzing
Block #92,012,960
22 transactions · 21 stateful · 2026-07-31 20:36:06 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,012,960 · 22 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
1w02w03w14w25w38w010w011w113w214w315w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1d41322…488c
0x7b9256…1fb2
12 touches
15 conflicts
0xc1d41322…488d
0x7b9256…1fb2
12 touches
15 conflicts
0xde1a77d4…afa7
0x7b9256…1fb2
12 touches
15 conflicts
0xde1a77d4…afa8
0x7b9256…1fb2
12 touches
15 conflicts
0xde1a77d4…afab
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 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 0xc1d41322f1…04488c
Audit this contract →
← previous block·next block →recent activity