← previous blocknext block →recent activity
Analyzing
Block #84,047,926
46 transactions · 34 stateful · 2026-06-27 14:13:22 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,047,926 · 46 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
1w02w13w24w38w49w511w612w729w536w438w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49194594…2c70
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
14 touches
21 conflicts
0x8726ff39…3be8
0x34b655…2a6f
12 touches
15 conflicts
0xac9ebc91…1fdd
0xd32edf…ff58
11 touches
15 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 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 0x4919459402…d42c70
Audit this contract →
← previous block·next block →recent activity