← previous blocknext block →recent activity
Analyzing
Block #84,073,466
30 transactions · 26 stateful · 2026-06-27 17:03:26 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,073,466 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w69w724w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x1d2a8430…30bf
0xa6afd3…d132
10 touches
10 conflicts
0x32359294…7113
0x34b655…2a6f
10 touches
10 conflicts
0xc4a440d1…f0ed
0xd32edf…ff58
9 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3de5fb8b…400a
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…002c
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity