← previous blocknext block →recent activity
Analyzing
Block #83,615,508
82 transactions · 62 stateful · 2026-06-25 14:09:28 UTC
Parallelism
79/100
Blocked
79%
Avg conflicts / tx
3.22
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,615,508 · 82 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w09w113w114w216w317w420w023w124w225w326w427w528w662w567w2
- 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
20 touches
45 conflicts
0x94e7f277…471b
0x34b655…2a6f
14 touches
21 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
14 touches
21 conflicts
0xf8fd1cbd…d093
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x40970e69…da50
0x69df8a…6292
12 touches
15 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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
136 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity