← previous blocknext block →recent activity
Analyzing
Block #83,482,710
56 transactions · 46 stateful · 2026-06-24 23:23:37 UTC
Parallelism
68/100
Blocked
78%
Avg conflicts / tx
2.89
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,482,710 · 56 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
1w02w03w16w07w08w19w110w011w113w214w216w317w419w420w521w622w742w543w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
14 touches
21 conflicts
0x19ce481d…6c36
0x34b655…2a6f
12 touches
15 conflicts
0x9ff2b017…3fa2
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity