← previous blocknext block →recent activity
Analyzing
Block #83,758,231
66 transactions · 56 stateful · 2026-06-26 06:01:52 UTC
Parallelism
68/100
Blocked
79%
Avg conflicts / tx
4.92
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,758,231 · 66 txs across 21 waves · depth 21
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w217w418w520w621w723w825w926w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
42 touches
210 conflicts
0x2484cc15…5afc
0x34b655…2a6f
24 touches
66 conflicts
0xe02484a6…c32e
0xc8689a…ee79
24 touches
66 conflicts
0xae62b3af…e14f
0x34b655…2a6f
24 touches
66 conflicts
0x5941ac48…c525
0x34b655…2a6f
24 touches
66 conflicts
0xefd12093…3a22
0xd32edf…ff58
19 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xba5743c7…21c5
0x1b6862…e19c
14 touches
21 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
210 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity