← previous blocknext block →recent activity
Analyzing
Block #92,060,845
19 transactions · 18 stateful · 2026-08-01 00:36:56 UTC
Parallelism
42/100
Blocked
61%
Avg conflicts / tx
2.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #92,060,845 · 19 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w711w812w913w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b4767df…8698
0x7b9256…1fb2
22 touches
55 conflicts
0x177211e2…1c2d
0x754704…b603
22 touches
55 conflicts
0xe1f61186…e2f8
0x754704…b603
22 touches
55 conflicts
0x00000000…0006
0x7b9256…1fb2
22 touches
55 conflicts
0x01d66e06…aff9
0x7b9256…1fb2
22 touches
55 conflicts
0x01d66e06…affa
0x7b9256…1fb2
22 touches
55 conflicts
0x01d66e06…affd
0x7b9256…1fb2
22 touches
55 conflicts
0x5b4767df…8697
0x7b9256…1fb2
22 touches
55 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
55 conflicts on slot 0x5b4767dfa7…e68698
Audit this contract →
← previous block·next block →recent activity