← previous blocknext block →recent activity
Analyzing
Block #83,617,408
38 transactions · 34 stateful · 2026-06-25 14:22:11 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,617,408 · 38 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
1w02w13w24w37w08w09w410w516w017w118w219w620w221w322w424w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xda2a863b…e2e8
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0003
0x019883…2a9a
10 touches
10 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
10 touches
10 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity