← previous blocknext block →recent activity
Analyzing
Block #83,633,130
57 transactions · 52 stateful · 2026-06-25 16:07:16 UTC
Parallelism
68/100
Blocked
79%
Avg conflicts / tx
4.3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,633,130 · 57 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w510w611w712w813w914w1015w1116w1217w1318w1419w1545w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
20 touches
45 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
20 touches
45 conflicts
0x8e739938…e7ab
0x34b655…2a6f
20 touches
45 conflicts
0x40970e69…da50
0x69df8a…6292
20 touches
45 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
20 touches
45 conflicts
0xdb067026…9eb8
0x69df8a…6292
20 touches
45 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
136 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity