← previous blocknext block →recent activity
Analyzing
Block #83,616,498
65 transactions · 47 stateful · 2026-06-25 14:16:05 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.75
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,616,498 · 65 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w114w117w220w321w427w148w550w251w252w353w454w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x37a276a3…673f
0x34b655…2a6f
16 touches
28 conflicts
0x2484cc15…5afc
0x34b655…2a6f
14 touches
21 conflicts
0x5941ac48…c525
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x08b98386…d3ee
0xd32edf…ff58
11 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x821f0b86…7ebb
0x34b655…2a6f
10 touches
10 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity