← previous blocknext block →recent activity
Analyzing
Block #83,668,263
32 transactions · 28 stateful · 2026-06-25 20:01:42 UTC
Parallelism
59/100
Blocked
68%
Avg conflicts / tx
2.38
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,668,263 · 32 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
2w05w16w27w08w19w010w113w214w315w416w517w618w719w820w921w1022w1124w625w1227w929w1030w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
10 touches
10 conflicts
0xde696e46…6446
0x34b655…2a6f
8 touches
6 conflicts
0xf5970b31…f34c
0x34b655…2a6f
8 touches
6 conflicts
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xcd10e72b…c630
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity