← previous blocknext block →recent activity
Analyzing
Block #83,199,272
13 transactions · 11 stateful · 2026-06-23 15:50:17 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,199,272 · 13 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x557a7012…4100
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x5b02bccd…e76b
0x065c9d…c394
2 touches
0 conflicts
0x77359264…90f0
0x065c9d…c394
2 touches
0 conflicts
0xa1a10194…fe7d
0x065c9d…c394
2 touches
0 conflicts
0xa5c26a8d…f2ea
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
3 conflicts on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity