← previous blocknext block →recent activity
Analyzing
Block #84,334,639
70 transactions · 58 stateful · 2026-06-28 22:03:10 UTC
Parallelism
69/100
Blocked
78%
Avg conflicts / tx
4.07
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #84,334,639 · 70 txs across 22 waves · depth 22
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w117w130w633w856w957w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
36 touches
153 conflicts
0xd26829b6…f416
0xd32edf…ff58
19 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
16 touches
28 conflicts
0x75194ada…a1c5
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
16 touches
28 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
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