← previous blocknext block →recent activity
Analyzing
Block #92,297,267
17 transactions · 16 stateful · 2026-08-01 20:25:59 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,297,267 · 17 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
1w02w15w06w17w28w310w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x501ee0a1…512b
0x7b9256…1fb2
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x3ba257ee…623c
0x7b9256…1fb2
8 touches
6 conflicts
0x3ba257ee…623d
0x7b9256…1fb2
8 touches
6 conflicts
0x3ba257ee…6240
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 0x501ee0a1c7…72512b
Audit this contract →
← previous block·next block →recent activity