← previous blocknext block →recent activity
Analyzing
Block #83,616,619
65 transactions · 53 stateful · 2026-06-25 14:16:54 UTC
Parallelism
63/100
Blocked
91%
Avg conflicts / tx
6.2
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #83,616,619 · 65 txs across 24 waves · depth 24
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
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w716w818w919w1021w1122w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
46 touches
253 conflicts
0x1c58d38b…0f1a
0xd32edf…ff58
25 touches
78 conflicts
0x59d2aa91…a39a
0x34b655…2a6f
24 touches
66 conflicts
0x2484cc15…5afc
0x34b655…2a6f
22 touches
55 conflicts
0x5941ac48…c525
0x34b655…2a6f
22 touches
55 conflicts
0xe02484a6…c32e
0xc8689a…ee79
22 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
253 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity