← previous blocknext block →recent activity
Analyzing
Block #83,615,459
55 transactions · 44 stateful · 2026-06-25 14:09:08 UTC
Parallelism
64/100
Blocked
77%
Avg conflicts / tx
3.45
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,615,459 · 55 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w011w113w116w217w118w320w423w541w542w643w748w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x75cdffd8…c217
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
16 touches
28 conflicts
0xad0047c2…4eb1
0xd32edf…ff58
13 touches
21 conflicts
0x2484cc15…5afc
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x5941ac48…c525
0x34b655…2a6f
12 touches
15 conflicts
0xd6d4eb00…30f3
0x34b655…2a6f
12 touches
15 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity