← previous blocknext block →recent activity
Analyzing
Block #84,705,497
57 transactions · 43 stateful · 2026-06-30 15:15:55 UTC
Parallelism
67/100
Blocked
74%
Avg conflicts / tx
2.46
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #84,705,497 · 57 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
1w02w13w24w36w010w111w212w313w425w026w127w029w130w241w244w545w649w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
10 touches
10 conflicts
0xe732567d…b65d
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity