← previous blocknext block →recent activity
Analyzing
Block #83,661,024
27 transactions · 24 stateful · 2026-06-25 19:13:24 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.74
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,661,024 · 27 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
1w02w13w24w35w46w511w012w115w216w317w418w520w726w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46d5a052…ff2e
0x34b655…2a6f
14 touches
21 conflicts
0x596db964…7935
0xd32edf…ff58
11 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x44d7acbf…e67e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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 0x46d5a0529d…adff2e
Audit this contract →
← previous block·next block →recent activity