← previous blocknext block →recent activity
Analyzing
Block #92,007,263
20 transactions · 17 stateful · 2026-07-31 20:07:27 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,007,263 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w38w49w510w611w712w113w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fe1e559…7d6f
0x7b9256…1fb2
16 touches
28 conflicts
0x0fe1e559…7d70
0x7b9256…1fb2
16 touches
28 conflicts
0x177211e2…1c2d
0x754704…b603
16 touches
28 conflicts
0xe1f61186…e2f8
0x754704…b603
16 touches
28 conflicts
0x00000000…0006
0x7b9256…1fb2
16 touches
28 conflicts
0xab926d26…3a5d
0x7b9256…1fb2
16 touches
28 conflicts
0xab926d26…3a5a
0x7b9256…1fb2
16 touches
28 conflicts
0xab926d26…3a59
0x7b9256…1fb2
16 touches
28 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
28 conflicts on slot 0x0fe1e5590b…8a7d6f
Audit this contract →
← previous block·next block →recent activity