← previous blocknext block →recent activity
Analyzing
Block #84,705,655
42 transactions · 35 stateful · 2026-06-30 15:16:58 UTC
Parallelism
57/100
Blocked
77%
Avg conflicts / tx
3.1
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #84,705,655 · 42 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w29w313w014w127w528w333w934w1035w1141w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0x8d691210…341b
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x9f40a209…1193
0x34b655…2a6f
10 touches
10 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity