← previous blocknext block →recent activity
Analyzing
Block #84,317,735
46 transactions · 39 stateful · 2026-06-28 20:10:32 UTC
Parallelism
61/100
Blocked
74%
Avg conflicts / tx
3.33
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #84,317,735 · 46 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w19w210w311w412w513w614w315w734w735w837w938w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x75cdffd8…c217
0x34b655…2a6f
22 touches
55 conflicts
0xe02484a6…c32e
0xc8689a…ee79
18 touches
36 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
18 touches
36 conflicts
0x75194ada…a1c5
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity