← previous blocknext block →recent activity
Analyzing
Block #83,399,243
36 transactions · 31 stateful · 2026-06-24 14:06:12 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,399,243 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w312w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678a8de3…7da5
0x34b655…2a6f
14 touches
21 conflicts
0xd84eb727…a622
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xf8480e2a…dff4
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
21 conflicts on slot 0x678a8de356…df7da5
Audit this contract →
← previous block·next block →recent activity