← previous blocknext block →recent activity
Analyzing
Block #92,409,406
21 transactions · 19 stateful · 2026-08-02 05:49:55 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,409,406 · 21 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
4w05w06w17w28w312w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bf21aae…9ff5
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
0x119b517b…7ae8
0x7b9256…1fb2
8 touches
6 conflicts
0x119b517b…7ae9
0x7b9256…1fb2
8 touches
6 conflicts
0x9bf21aae…9ff6
0x7b9256…1fb2
8 touches
6 conflicts
0x9bf21aae…9ff9
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 0x9bf21aae11…ec9ff5
Audit this contract →
← previous block·next block →recent activity