← previous blocknext block →recent activity
Analyzing
Block #92,064,528
17 transactions · 16 stateful · 2026-08-01 00:55:28 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,064,528 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w18w09w110w211w213w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x0661d478…6139
0x7b9256…1fb2
6 touches
3 conflicts
0x1a7c9214…55ef
0x7b9256…1fb2
6 touches
3 conflicts
0x1a7c9214…55f0
0x7b9256…1fb2
6 touches
3 conflicts
0x1a7c9214…55f3
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x0661d478…6138
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 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity