← previous blocknext block →recent activity
Analyzing
Block #83,636,138
38 transactions · 31 stateful · 2026-06-25 16:27:22 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
1.63
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,636,138 · 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
1w02w13w04w05w06w17w08w19w214w115w218w119w020w321w422w523w624w726w627w134w1135w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xc983cab3…daa5
0x34b655…2a6f
8 touches
6 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
8 touches
6 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
6 touches
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity