← previous blocknext block →recent activity
Analyzing
Block #83,654,517
33 transactions · 27 stateful · 2026-06-25 18:30:03 UTC
Parallelism
58/100
Blocked
74%
Avg conflicts / tx
2.03
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,654,517 · 33 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
1w02w13w04w15w210w011w112w215w216w317w419w620w722w323w224w326w829w1030w1131w1232w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x8f4c5cb2…cbee
0x34b655…2a6f
10 touches
10 conflicts
0xac61d3a4…7da8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0836218c…2d68
0x34b655…2a6f
6 touches
3 conflicts
0x939a5d3a…3c36
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
15 conflicts on slot 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity