← previous blocknext block →recent activity
Analyzing
Block #92,530,711
17 transactions · 16 stateful · 2026-08-02 16:00:02 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,530,711 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w18w29w113w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa51de3df…c65a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x75b55c66…4173
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa4e01136…e0fc
0x40c49f…2af0
5 touches
3 conflicts
0x7354aa9c…e1c9
0x34b655…2a6f
4 touches
1 conflict
0x7da56943…9753
0x34b655…2a6f
4 touches
1 conflict
0x95931da4…d8b2
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0xa51de3dfe9…dec65a
Audit this contract →
← previous block·next block →recent activity