← previous blocknext block →recent activity
Analyzing
Block #84,353,408
31 transactions · 28 stateful · 2026-06-29 00:08:20 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,353,408 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w47w48w09w112w013w114w218w519w421w526w327w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x454d8940…cfe7
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
8 touches
6 conflicts
0x0a6cb118…4ca4
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x42a27aab…c655
0xd32edf…ff58
7 touches
6 conflicts
0xc08384da…ecb7
0x34b655…2a6f
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
10 conflicts on slot 0x454d8940c1…fbcfe7
Audit this contract →
← previous block·next block →recent activity