← previous blocknext block →recent activity
Analyzing
Block #83,628,469
44 transactions · 35 stateful · 2026-06-25 15:36:08 UTC
Parallelism
61/100
Blocked
77%
Avg conflicts / tx
2.61
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,628,469 · 44 txs across 17 waves · depth 17
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
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w112w415w016w117w218w319w420w021w122w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x2e86dd1e…dc3e
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
12 touches
15 conflicts
0x55c19be0…00a2
0x34b655…2a6f
12 touches
15 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity