← previous blocknext block →recent activity
Analyzing
Block #83,625,490
51 transactions · 38 stateful · 2026-06-25 15:16:11 UTC
Parallelism
74/100
Blocked
66%
Avg conflicts / tx
1.61
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,625,490 · 51 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w19w210w012w313w414w215w016w121w025w026w127w128w229w330w435w536w337w140w441w643w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x99aef669…6c0a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x7b72fd15…b096
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x485d2778…aa5d
0x1b6862…e19c
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity