← previous blocknext block →recent activity
Analyzing
Block #83,628,713
21 transactions · 20 stateful · 2026-06-25 15:37:46 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,628,713 · 21 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
1w02w13w04w15w06w17w28w39w410w511w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda5e0705…ecb9
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
14 touches
21 conflicts
0x5396d712…a139
0x34b655…2a6f
14 touches
21 conflicts
0x40812443…9d08
0x34b655…2a6f
10 touches
10 conflicts
0xf2b3aea5…2528
0x34b655…2a6f
8 touches
6 conflicts
0x5a3732cb…edaf
0x1b6862…e19c
4 touches
1 conflict
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 0xda5e0705c4…a5ecb9
Audit this contract →
← previous block·next block →recent activity