← previous blocknext block →recent activity
Analyzing
Block #83,452,713
23 transactions · 20 stateful · 2026-06-24 20:03:25 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,452,713 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w29w010w111w216w017w019w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49194594…2c70
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcadc2eec…bbf5
0x34b655…2a6f
4 touches
1 conflict
0xdf37a93d…879b
0x34b655…2a6f
4 touches
1 conflict
0xe304e27c…6026
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x4919459402…d42c70
Audit this contract →
← previous block·next block →recent activity