← previous blocknext block →recent activity
Analyzing
Block #84,510,010
54 transactions · 46 stateful · 2026-06-29 17:32:29 UTC
Parallelism
80/100
Blocked
74%
Avg conflicts / tx
1.93
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #84,510,010 · 54 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w115w216w318w420w521w522w643w844w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x02ab1951…b1e8
0xd32edf…ff58
11 touches
15 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0x235dd62b…f416
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity