← previous blocknext block →recent activity
Analyzing
Block #92,286,258
18 transactions · 18 stateful · 2026-08-01 19:30:37 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,286,258 · 18 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
1w02w13w25w06w17w29w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0xad26f381…7c76
0x7b9256…1fb2
6 touches
3 conflicts
0xad26f381…7c79
0x7b9256…1fb2
6 touches
3 conflicts
0xdcde2db0…d62d
0x7b9256…1fb2
6 touches
3 conflicts
0xdcde2db0…d62e
0x7b9256…1fb2
6 touches
3 conflicts
0xad26f381…7c75
0x7b9256…1fb2
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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