← previous blocknext block →recent activity
Analyzing
Block #83,482,288
23 transactions · 19 stateful · 2026-06-24 23:20:48 UTC
Parallelism
52/100
Blocked
68%
Avg conflicts / tx
2.39
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,482,288 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w17w08w19w210w311w412w517w518w620w821w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xfe4e62b8…9ade
0x34b655…2a6f
10 touches
11 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x18cbab19…7a73
0x34b655…2a6f
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity