← previous blocknext block →recent activity
Analyzing
Block #83,454,804
45 transactions · 35 stateful · 2026-06-24 20:17:24 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
1.71
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,454,804 · 45 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w07w08w110w212w315w217w018w123w224w325w426w327w328w429w530w633w138w739w843w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bdb0bbb…f5a2
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xbfe63d66…c3e6
0x34b655…2a6f
10 touches
10 conflicts
0xe063d1a9…62ce
0xd32edf…ff58
9 touches
10 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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
15 conflicts on slot 0x5bdb0bbb37…04f5a2
Audit this contract →
← previous block·next block →recent activity