← previous blocknext block →recent activity
Analyzing
Block #83,616,486
39 transactions · 35 stateful · 2026-06-25 14:16:01 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.49
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,616,486 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w18w212w013w114w215w316w417w518w621w424w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xb02054c6…0967
0x34b655…2a6f
10 touches
10 conflicts
0x9813b414…6fd7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xdf9957df…8d42
0x34b655…2a6f
8 touches
6 conflicts
0x48a29a03…c438
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity