← previous blocknext block →recent activity
Analyzing
Block #92,110,804
18 transactions · 16 stateful · 2026-08-01 04:48:11 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,110,804 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w010w111w213w214w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a36bde5…ce43
0x7b9256…1fb2
6 touches
3 conflicts
0x0a36bde5…ce44
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0xda0c9803…197b
0x7b9256…1fb2
6 touches
3 conflicts
0xda0c9803…197a
0x7b9256…1fb2
6 touches
3 conflicts
0x0a36bde5…ce47
0x7b9256…1fb2
6 touches
3 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
3 conflicts on slot 0x0a36bde519…1dce43
Audit this contract →
← previous block·next block →recent activity