← previous blocknext block →recent activity
Analyzing
Block #83,494,272
14 transactions · 9 stateful · 2026-06-25 00:40:42 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,494,272 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x6c0b6cb5…372c
0x065c9d…c394
3 touches
1 conflict
0x05319371…4cbe
0x065c9d…c394
2 touches
0 conflicts
0x31095185…b64e
0x065c9d…c394
2 touches
0 conflicts
0x563b7cd3…b2dc
0x065c9d…c394
2 touches
0 conflicts
0x6dc07b30…9f2e
0x065c9d…c394
2 touches
0 conflicts
0x9658e6f7…4ff0
0x065c9d…c394
2 touches
0 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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity