← previous blocknext block →recent activity
Analyzing
Block #83,468,373
16 transactions · 13 stateful · 2026-06-24 21:48:03 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,468,373 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w011w212w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x67559a4e…a4d6
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8615e83…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xd07e04ea…7c9e
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity