← previous blocknext block →recent activity
Analyzing
Block #83,617,904
55 transactions · 47 stateful · 2026-06-25 14:25:30 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
3.02
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,617,904 · 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
1w02w13w24w35w46w511w113w014w116w217w318w619w720w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xda0030ac…df3c
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x45b67460…28a8
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x664bf99e…0a8c
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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity