← previous blocknext block →recent activity
Analyzing
Block #84,460,344
78 transactions · 54 stateful · 2026-06-29 12:01:03 UTC
Parallelism
76/100
Blocked
76%
Avg conflicts / tx
3.29
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #84,460,344 · 78 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w320w421w522w624w726w827w828w930w1031w1133w964w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
24 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0x35de07e6…7751
0x34b655…2a6f
20 touches
45 conflicts
0x826cce18…251c
0x34b655…2a6f
20 touches
45 conflicts
0xe02484a6…c32e
0xc8689a…ee79
20 touches
45 conflicts
0xdce4ee49…2af7
0xd32edf…ff58
17 touches
36 conflicts
0xc05b880b…7746
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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity