← previous blocknext block →recent activity
Analyzing
Block #84,461,282
88 transactions · 63 stateful · 2026-06-29 12:07:20 UTC
Parallelism
73/100
Blocked
76%
Avg conflicts / tx
3.09
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #84,461,282 · 88 txs across 24 waves · depth 24
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
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w433w837w982w1083w1184w1285w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xdf6ed12d…f623
0xd32edf…ff58
21 touches
55 conflicts
0xe02484a6…c32e
0xc8689a…ee79
20 touches
45 conflicts
0x64b219d4…a178
0x34b655…2a6f
18 touches
36 conflicts
0x78a3ac38…9fbf
0x34b655…2a6f
18 touches
36 conflicts
0x910be0f4…b71c
0x34b655…2a6f
18 touches
36 conflicts
0xabf57eb6…416d
0x34b655…2a6f
18 touches
36 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
18 touches
36 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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity