← previous blocknext block →recent activity
Analyzing
Block #84,452,139
43 transactions · 35 stateful · 2026-06-29 11:06:21 UTC
Parallelism
65/100
Blocked
66%
Avg conflicts / tx
1.67
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #84,452,139 · 43 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w19w212w313w414w315w016w120w021w122w223w324w425w526w630w331w432w738w11
- 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
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xa5f1d2ef…822e
0x34b655…2a6f
10 touches
10 conflicts
0x2d68f9b1…1abb
0xd32edf…ff58
9 touches
10 conflicts
0x826cce18…251c
0x34b655…2a6f
8 touches
6 conflicts
0x35de07e6…7751
0x34b655…2a6f
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