← previous blocknext block →recent activity
Analyzing
Block #83,452,462
68 transactions · 53 stateful · 2026-06-24 20:01:44 UTC
Parallelism
68/100
Blocked
75%
Avg conflicts / tx
4.04
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #83,452,462 · 68 txs across 22 waves · depth 22
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
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w411w513w415w521w853w954w1055w1156w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x32359294…7113
0x34b655…2a6f
32 touches
120 conflicts
0xe6950848…9ff6
0x34b655…2a6f
28 touches
91 conflicts
0xe02484a6…c32e
0xc8689a…ee79
28 touches
91 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
28 touches
91 conflicts
0x2e3da4d7…9533
0xd32edf…ff58
21 touches
55 conflicts
0x07b5c6c6…886a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 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