← previous blocknext block →recent activity
Analyzing
Block #83,842,729
65 transactions · 45 stateful · 2026-06-26 15:25:49 UTC
Parallelism
68/100
Blocked
78%
Avg conflicts / tx
3.2
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #83,842,729 · 65 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
1w02w13w24w35w47w113w214w515w616w717w818w919w1021w1152w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xd75687a6…21c7
0xd32edf…ff58
15 touches
28 conflicts
0x8726ff39…3be8
0x34b655…2a6f
14 touches
21 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
14 touches
21 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x5df6102c…6494
0xa6afd3…d132
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity