← previous blocknext block →recent activity
Analyzing
Block #83,636,535
33 transactions · 29 stateful · 2026-06-25 16:30:02 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,636,535 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w010w011w112w017w118w119w220w321w425w129w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x672fd8ba…9e9e
0x34b655…2a6f
12 touches
15 conflicts
0xd18a8dca…452c
0x1b6862…e19c
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd58b9a66…1c23
0x34b655…2a6f
8 touches
6 conflicts
0x57fba152…00d5
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x672fd8ba57…cf9e9e
Audit this contract →
← previous block·next block →recent activity