← previous blocknext block →recent activity
Analyzing
Block #83,401,070
69 transactions · 32 stateful · 2026-06-24 14:18:25 UTC
Parallelism
72/100
Blocked
66%
Avg conflicts / tx
1.36
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,401,070 · 69 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
1w02w15w16w214w020w124w226w328w429w535w639w743w849w953w1055w1166w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
24 touches
66 conflicts
0x8e507257…71c1
0x34b655…2a6f
18 touches
36 conflicts
0xf5f29db8…11a3
0x34b655…2a6f
18 touches
36 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
10 touches
10 conflicts
0x3d26964d…53cd
0x34b655…2a6f
10 touches
10 conflicts
0xb6b9800d…0682
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x3c78ca04…432c
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
66 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity