← previous blocknext block →recent activity
Analyzing
Block #84,492,015
66 transactions · 44 stateful · 2026-06-29 15:32:24 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
3.48
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #84,492,015 · 66 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
9w010w111w212w313w416w519w620w022w133w034w135w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
20 touches
45 conflicts
0xfefb0189…f726
0x34b655…2a6f
20 touches
45 conflicts
0x62554ce4…109e
0x34b655…2a6f
20 touches
45 conflicts
0xec85756f…0ba2
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0xe2e45419…f17b
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
171 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity