← previous blocknext block →recent activity
Analyzing
Block #92,560,717
12 transactions · 10 stateful · 2026-08-02 18:30:55 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,560,717 · 12 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
1w02w15w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c119c6d…a42e
0x34b655…2a6f
4 touches
1 conflict
0xdadee63d…484c
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xb065ea3d…d420
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x177f744d…b7dd
0x34b655…2a6f
4 touches
1 conflict
0x56fee6ed…a8c4
0xd32edf…ff58
3 touches
1 conflict
0x9ae56910…fe50
0x34b655…2a6f
3 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
1 conflict on slot 0x0c119c6d6d…e8a42e
Audit this contract →
← previous block·next block →recent activity