← previous blocknext block →recent activity
Analyzing
Block #92,342,424
18 transactions · 15 stateful · 2026-08-02 00:13:05 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,342,424 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w09w110w211w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xd91e6afa…523a
0x7b9256…1fb2
8 touches
6 conflicts
0xd91e6afa…5236
0x7b9256…1fb2
8 touches
6 conflicts
0x3f007ab6…0a16
0x7b9256…1fb2
8 touches
6 conflicts
0xd91e6afa…5237
0x7b9256…1fb2
8 touches
6 conflicts
0x3f007ab6…0a15
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
6 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity