← previous blocknext block →recent activity
Analyzing
Block #84,064,271
76 transactions · 53 stateful · 2026-06-27 16:02:18 UTC
Parallelism
70/100
Blocked
77%
Avg conflicts / tx
3.33
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #84,064,271 · 76 txs across 23 waves · depth 23
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
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w118w219w521w623w724w625w827w963w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
36 touches
153 conflicts
0x0efc210e…70ab
0x34b655…2a6f
20 touches
45 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
20 touches
45 conflicts
0xe1e58d05…117f
0x34b655…2a6f
20 touches
45 conflicts
0xc0ce279f…43ad
0xd32edf…ff58
19 touches
45 conflicts
0x489bff18…82f3
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
16 touches
28 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
153 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity