← previous blocknext block →recent activity
Analyzing
Block #83,412,288
44 transactions · 34 stateful · 2026-06-24 15:33:22 UTC
Parallelism
75/100
Blocked
65%
Avg conflicts / tx
1.75
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,412,288 · 44 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w412w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xa2fc508b…60f6
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
12 touches
15 conflicts
0xd1480c90…ae0b
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity