← previous blocknext block →recent activity
Analyzing
Block #83,196,394
13 transactions · 9 stateful · 2026-06-23 15:31:02 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,196,394 · 13 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
1w02w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58710ab…1d98
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x38fec2d1…7437
0x065c9d…c394
3 touches
1 conflict
0x22e61628…7503
0x065c9d…c394
2 touches
0 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x420a05e3…dcf7
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
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 0xf58710ab6c…191d98
Audit this contract →
← previous block·next block →recent activity