← previous blocknext block →recent activity
Analyzing
Block #82,553,041
13 transactions · 11 stateful · 2026-06-20 15:48:44 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,553,041 · 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
1w02w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xdc410f17…ce26
0x065c9d…c394
3 touches
1 conflict
0xbdaa63eb…0423
0x065c9d…c394
3 touches
1 conflict
0x5de75f1a…efb0
0x065c9d…c394
2 touches
0 conflicts
0x60199a17…868c
0x065c9d…c394
2 touches
0 conflicts
0x6b00551e…39e0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity