← previous blocknext block →recent activity
Analyzing
Block #83,627,629
34 transactions · 28 stateful · 2026-06-25 15:30:30 UTC
Parallelism
59/100
Blocked
79%
Avg conflicts / tx
2.15
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,627,629 · 34 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w59w610w011w115w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x3617b7a4…79a2
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe01158fd…f97f
0x1b6862…e19c
8 touches
6 conflicts
0x13aceb70…cf9f
0x34b655…2a6f
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