← previous blocknext block →recent activity
Analyzing
Block #83,634,040
58 transactions · 46 stateful · 2026-06-25 16:13:21 UTC
Parallelism
69/100
Blocked
61%
Avg conflicts / tx
2.02
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,634,040 · 58 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w310w412w013w114w226w027w128w229w330w438w445w446w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x9ad4d28a…c788
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6c807d8e…9cc9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x3bd55803…5d4b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity