← previous blocknext block →recent activity
Analyzing
Block #83,631,919
36 transactions · 33 stateful · 2026-06-25 15:59:10 UTC
Parallelism
58/100
Blocked
73%
Avg conflicts / tx
2.56
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,631,919 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w111w012w013w114w215w316w417w518w619w720w821w922w1023w430w131w1133w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5cc8dd43…8cf2
0x34b655…2a6f
9 touches
12 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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity