← previous blocknext block →recent activity
Analyzing
Block #83,654,711
31 transactions · 29 stateful · 2026-06-25 18:31:20 UTC
Parallelism
55/100
Blocked
69%
Avg conflicts / tx
2.55
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,654,711 · 31 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
1w03w14w25w37w08w19w010w111w212w313w414w515w616w717w822w224w826w1028w1129w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x3ca49d36…1280
0x34b655…2a6f
14 touches
21 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x487922c6…dbd2
0x34b655…2a6f
12 touches
15 conflicts
0x7c44530b…0ce3
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
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 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity