← previous blocknext block →recent activity
Analyzing
Block #92,113,865
14 transactions · 14 stateful · 2026-08-01 05:03:35 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,113,865 · 14 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
1w03w14w25w36w07w18w29w310w411w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xeef20f25…a242
0x7b9256…1fb2
10 touches
10 conflicts
0xeef20f25…a241
0x7b9256…1fb2
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x91f4e3fd…9f51
0x7b9256…1fb2
10 touches
10 conflicts
0xeef20f25…a245
0x7b9256…1fb2
10 touches
10 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
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity