← previous blocknext block →recent activity
Analyzing
Block #92,201,707
14 transactions · 13 stateful · 2026-08-01 12:25:22 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,201,707 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x0df5574e…d4db
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xff196840…a453
0x34b655…2a6f
10 touches
10 conflicts
0x3e3b859f…3654
0x34b655…2a6f
6 touches
3 conflicts
0x69017fce…85c1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity