← previous blocknext block →recent activity
Analyzing
Block #92,212,832
17 transactions · 16 stateful · 2026-08-01 13:21:19 UTC
Parallelism
53/100
Blocked
56%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,212,832 · 17 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
4w05w16w27w08w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea080e6…cd40
0x7b9256…1fb2
16 touches
28 conflicts
0x7ea080e6…cd3f
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
0x52a3e238…0b3e
0x7b9256…1fb2
16 touches
28 conflicts
0x52a3e238…0b3f
0x7b9256…1fb2
16 touches
28 conflicts
0x52a3e238…0b42
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 0x7ea080e6d5…d9cd40
Audit this contract →
← previous block·next block →recent activity