← previous blocknext block →recent activity
Analyzing
Block #92,261,208
12 transactions · 11 stateful · 2026-08-01 17:24:37 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,261,208 · 12 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
1w02w13w24w35w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xfbf7e94d…74de
0x34b655…2a6f
6 touches
3 conflicts
0x71784e3b…0f0a
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x45ed2321…28db
0x7b9256…1fb2
4 touches
1 conflict
0x45ed2321…28dc
0x7b9256…1fb2
4 touches
1 conflict
0x45ed2321…28df
0x7b9256…1fb2
4 touches
1 conflict
0x71784e3b…0f09
0x7b9256…1fb2
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity