← previous blocknext block →recent activity
Analyzing
Block #83,853,494
80 transactions · 55 stateful · 2026-06-26 16:37:41 UTC
Parallelism
75/100
Blocked
76%
Avg conflicts / tx
2.9
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,853,494 · 80 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w310w011w113w214w316w418w519w621w722w824w959w1165w1267w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
20 touches
45 conflicts
0xe02484a6…c32e
0xc8689a…ee79
18 touches
36 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
18 touches
36 conflicts
0x8726ff39…3be8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity