← previous blocknext block →recent activity
Analyzing
Block #83,465,550
10 transactions · 10 stateful · 2026-06-24 21:29:12 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,465,550 · 10 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x88151f6a…8356
0x065c9d…c394
4 touches
1 conflict
0x310817f8…5f80
0x065c9d…c394
4 touches
1 conflict
0x3a0f2a2d…dfe4
0x065c9d…c394
3 touches
1 conflict
0x6c2e36dc…b45c
0x065c9d…c394
3 touches
1 conflict
0xff96dc9b…93d7
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
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity