← previous blocknext block →recent activity
Analyzing
Block #83,652,504
24 transactions · 24 stateful · 2026-06-25 18:16:40 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,652,504 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w37w08w19w010w111w212w313w416w517w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xb6b7c45d…9d5a
0x34b655…2a6f
10 touches
10 conflicts
0xf86f15cd…38af
0x34b655…2a6f
8 touches
6 conflicts
0x7a12a7ab…4c45
0x34b655…2a6f
6 touches
3 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity