← previous blocknext block →recent activity
Analyzing
Block #84,426,612
40 transactions · 37 stateful · 2026-06-29 08:16:15 UTC
Parallelism
75/100
Blocked
68%
Avg conflicts / tx
2.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,426,612 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w27w310w411w527w328w429w430w531w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x59a0baea…c9ba
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x32329fca…2d8c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x17ca7036…1e17
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity