← previous blocknext block →recent activity
Analyzing
Block #83,642,642
28 transactions · 28 stateful · 2026-06-25 17:10:49 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1.36
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,642,642 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w19w010w111w212w313w414w015w018w119w221w524w825w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
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
15 conflicts on slot 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity