← previous blocknext block →recent activity
Analyzing
Block #92,006,017
20 transactions · 15 stateful · 2026-07-31 20:01:11 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,006,017 · 20 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
2w05w16w07w18w29w310w411w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac7f488…7841
0x7b9256…1fb2
12 touches
15 conflicts
0x0ac7f488…783e
0x7b9256…1fb2
12 touches
15 conflicts
0x00000000…0006
0x7b9256…1fb2
12 touches
15 conflicts
0x0ac7f488…783d
0x7b9256…1fb2
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0xe1f61186…e2f8
0x754704…b603
12 touches
15 conflicts
0x4c654988…bf90
0x7b9256…1fb2
12 touches
15 conflicts
0x4c654988…bf8f
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 0x0ac7f48822…ee7841
Audit this contract →
← previous block·next block →recent activity