← previous blocknext block →recent activity
Analyzing
Block #83,626,507
52 transactions · 41 stateful · 2026-06-25 15:23:00 UTC
Parallelism
69/100
Blocked
61%
Avg conflicts / tx
1.65
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,626,507 · 52 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w08w19w210w311w012w119w021w124w025w126w227w328w429w530w631w737w239w147w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xdf9957df…8d42
0x34b655…2a6f
14 touches
21 conflicts
0xdb19247d…233c
0x34b655…2a6f
12 touches
15 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
12 touches
15 conflicts
0x5fad6fee…7714
0x34b655…2a6f
12 touches
15 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
8 touches
6 conflicts
0x213ee207…a151
0x69df8a…6292
8 touches
6 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity