← previous blocknext block →recent activity
Analyzing
Block #83,452,284
31 transactions · 21 stateful · 2026-06-24 20:00:32 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,452,284 · 31 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
4w05w16w17w28w313w014w120w021w124w025w426w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02e5cdd…76b8
0x34b655…2a6f
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x4564d3f1…d001
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x12dd43c9…22d9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0xa02e5cdd28…1376b8
Audit this contract →
← previous block·next block →recent activity