← previous blocknext block →recent activity
Analyzing
Block #83,617,410
38 transactions · 34 stateful · 2026-06-25 14:22:11 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
1.82
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,617,410 · 38 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w37w38w29w310w411w315w116w017w118w219w320w421w522w523w624w725w833w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
10 touches
10 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
8 touches
6 conflicts
0xd7add284…8d28
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity