← previous blocknext block →recent activity
Analyzing
Block #83,400,875
77 transactions · 38 stateful · 2026-06-24 14:17:07 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
1.51
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,400,875 · 77 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w110w011w115w025w133w239w343w446w549w650w754w767w270w372w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0xf6476f21…3580
0x34b655…2a6f
16 touches
28 conflicts
0xef3a4217…dec8
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x9c7571b3…9605
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
12 touches
15 conflicts
0x54b48991…ab1e
0x34b655…2a6f
10 touches
10 conflicts
0xf794ac9a…a94c
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity