← previous blocknext block →recent activity
Analyzing
Block #83,627,776
30 transactions · 26 stateful · 2026-06-25 15:31:29 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
2.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,627,776 · 30 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
1w02w13w24w35w46w27w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13aceb70…cf9f
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x07d38027…0cd8
0xd32edf…ff58
13 touches
21 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x10c19272…7442
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
28 conflicts on slot 0x13aceb701e…58cf9f
Audit this contract →
← previous block·next block →recent activity