← previous blocknext block →recent activity
Analyzing
Block #83,410,214
42 transactions · 38 stateful · 2026-06-24 15:19:33 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
2.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,410,214 · 42 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w07w18w29w311w012w314w115w218w422w527w132w835w936w1038w1240w14
- 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
14 touches
21 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x4564d3f1…d001
0x34b655…2a6f
8 touches
6 conflicts
0x604d1daf…bf48
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity