← previous blocknext block →recent activity
Analyzing
Block #83,616,369
38 transactions · 34 stateful · 2026-06-25 14:15:14 UTC
Parallelism
76/100
Blocked
59%
Avg conflicts / tx
1.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,616,369 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w510w416w017w118w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x9384a9c1…e630
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0x02fdb0f1…5b05
0x34b655…2a6f
8 touches
6 conflicts
0x5941ac48…c525
0x34b655…2a6f
8 touches
6 conflicts
0xd6d4eb00…30f3
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
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