← previous blocknext block →recent activity
Analyzing
Block #83,202,247
34 transactions · 23 stateful · 2026-06-23 16:10:11 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,202,247 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w012w314w315w417w018w121w522w227w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0xde6b917f…3a72
0xa6afd3…d132
6 touches
3 conflicts
0x1504aa7b…24ad
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x2fed4b7a…ded7
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0xef65bff33c…857c9d
Audit this contract →
← previous block·next block →recent activity