← previous blocknext block →recent activity
Analyzing
Block #83,580,106
10 transactions · 9 stateful · 2026-06-25 10:13:05 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,580,106 · 10 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x047d89e1…16a6
0x065c9d…c394
2 touches
0 conflicts
0x36e138b2…47a4
0x065c9d…c394
2 touches
0 conflicts
0x6af52653…de7b
0x065c9d…c394
2 touches
0 conflicts
0x6ec76231…b0ef
0x065c9d…c394
2 touches
0 conflicts
0xde542ead…c953
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: MarginAccount
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity