← previous blocknext block →recent activity
Analyzing
Block #82,685,317
13 transactions · 10 stateful · 2026-06-21 06:35:05 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,685,317 · 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5171bfde…1713
0x065c9d…c394
4 touches
1 conflict
0xae222fa7…4e13
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x30414485…40d4
0x065c9d…c394
4 touches
1 conflict
0x4a4778c0…6204
0x065c9d…c394
4 touches
1 conflict
0x57b73d86…2fcb
0x34b655…2a6f
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 0x5171bfde7c…981713
Audit this contract →
← previous block·next block →recent activity