← previous blocknext block →recent activity
Analyzing
Block #84,462,062
90 transactions · 68 stateful · 2026-06-29 12:12:33 UTC
Parallelism
72/100
Blocked
82%
Avg conflicts / tx
4.18
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #84,462,062 · 90 txs across 25 waves · depth 25
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
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w537w1239w1341w1478w1580w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe02484a6…c32e
0xc8689a…ee79
38 touches
171 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
30 touches
105 conflicts
0x29686688…0598
0xa6afd3…d132
26 touches
78 conflicts
0x0c969dde…6b06
0xa6afd3…d132
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
26 touches
78 conflicts
0xdb067026…9eb8
0x69df8a…6292
26 touches
78 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
26 touches
78 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
26 touches
78 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: Settlement / Helper
171 conflicts on slot 0xe02484a657…35c32e
Audit this contract →
← previous block·next block →recent activity