← previous blocknext block →recent activity
Analyzing
Block #83,638,894
25 transactions · 24 stateful · 2026-06-25 16:45:47 UTC
Parallelism
68/100
Blocked
46%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,638,894 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w17w08w29w310w411w512w613w718w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07a0dea2…ca8c
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xe64e6363…e676
0x34b655…2a6f
12 touches
15 conflicts
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 conflicts
0xc8d3a17e…3430
0xd32edf…ff58
7 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
28 conflicts on slot 0x07a0dea248…11ca8c
Audit this contract →
← previous block·next block →recent activity