← previous blocknext block →recent activity
Analyzing
Block #92,771,289
16 transactions · 14 stateful · 2026-08-03 12:11:13 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,771,289 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdb76710a…4d17
0xd32edf…ff58
3 touches
1 conflict
0x1bdaf6f8…86a1
0x3bd359…433a
2 touches
0 conflicts
0x544ac270…ab6b
0x3bd359…433a
2 touches
0 conflicts
0xd226f002…9afc
0x3bd359…433a
2 touches
0 conflicts
0xc5d32121…bdf3
0x3ef3d8…d9ae
2 touches
0 conflicts
0xc5d32121…bdf4
0x3ef3d8…d9ae
2 touches
0 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: Perpl
1 conflict on slot 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity