← previous blocknext block →recent activity
Analyzing
Block #83,630,316
15 transactions · 13 stateful · 2026-06-25 15:48:27 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,630,316 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w17w28w311w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82dd2252…e1ce
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
8 touches
6 conflicts
0x09d737b9…21cd
0x34b655…2a6f
8 touches
6 conflicts
0x4ed5e9eb…3218
0x34b655…2a6f
8 touches
6 conflicts
0x5396d712…a139
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001b
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
6 conflicts on slot 0x82dd22520c…26e1ce
Audit this contract →
← previous block·next block →recent activity