← previous blocknext block →recent activity
Analyzing
Block #83,617,137
38 transactions · 30 stateful · 2026-06-25 14:20:22 UTC
Parallelism
66/100
Blocked
70%
Avg conflicts / tx
1.71
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,617,137 · 38 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w29w210w112w214w315w316w017w118w019w120w221w322w423w524w625w726w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x75cdffd8…c217
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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