← previous blocknext block →recent activity
Analyzing
Block #84,359,429
39 transactions · 29 stateful · 2026-06-29 00:48:32 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,359,429 · 39 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
1w02w13w24w312w113w214w316w017w121w022w123w224w325w426w528w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x454d8940…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0x79007823…10db
0xd32edf…ff58
7 touches
6 conflicts
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0x0cdf9369…5331
0x34b655…2a6f
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0xaf1f5f57…8015
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity