← previous blocknext block →recent activity
Analyzing
Block #85,138,112
18 transactions · 17 stateful · 2026-07-02 15:22:19 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,138,112 · 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
1w02w13w07w08w19w010w112w213w315w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191c9934…f4f4
0x34b655…2a6f
6 touches
3 conflicts
0x3c7520fc…9ca3
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x4ca9afe5…748d
0x34b655…2a6f
6 touches
3 conflicts
0x97cd0b61…696d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdeddb1c8…0d40
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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: Perpl
3 conflicts on slot 0x191c9934e4…8cf4f4
Audit this contract →
← previous block·next block →recent activity