← previous blocknext block →recent activity
Analyzing
Block #85,987,129
30 transactions · 28 stateful · 2026-07-06 13:38:33 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,987,129 · 30 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
1w02w13w24w35w06w17w28w39w010w311w415w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xcec6c18b…dc5e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd18a8dca…452b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: Kuru Exchange: MarginAccount
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity