← previous blocknext block →recent activity
Analyzing
Block #82,684,671
14 transactions · 14 stateful · 2026-06-21 06:30:46 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,684,671 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fb55ee7…8ecc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xf57d7c72…f65b
0x065c9d…c394
3 touches
1 conflict
0x16a12a61…6692
0x065c9d…c394
2 touches
0 conflicts
0x193b23b5…9361
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity