← previous blocknext block →recent activity
Analyzing
Block #92,164,058
17 transactions · 16 stateful · 2026-08-01 09:16:03 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,164,058 · 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
3w06w17w28w09w110w211w315w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ee1cd1c…fdda
0x7b9256…1fb2
8 touches
6 conflicts
0x8a165a3f…a248
0x7b9256…1fb2
8 touches
6 conflicts
0x8a165a3f…a249
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x0ee1cd1c…fdd6
0x7b9256…1fb2
8 touches
6 conflicts
0x0ee1cd1c…fdd7
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0x0ee1cd1cef…21fdda
Audit this contract →
← previous block·next block →recent activity