← previous blocknext block →recent activity
Analyzing
Block #84,494,052
30 transactions · 24 stateful · 2026-06-29 15:46:00 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,494,052 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w08w115w016w117w218w319w420w521w624w228w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x8e739938…e7ab
0x34b655…2a6f
12 touches
15 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
10 touches
10 conflicts
0x44966858…1d1a
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x6c6f37ba…c209
0x1b6862…e19c
4 touches
1 conflict
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