← previous blocknext block →recent activity
Analyzing
Block #83,693,421
57 transactions · 45 stateful · 2026-06-25 22:49:33 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.81
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,693,421 · 57 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
2w06w07w18w09w110w211w312w114w015w120w021w022w123w224w325w426w527w632w134w239w541w644w648w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xb08ffb61…d6b8
0xd32edf…ff58
13 touches
21 conflicts
0xd2453506…54e4
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x081cde99…92ff
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity