← previous blocknext block →recent activity
Analyzing
Block #81,408,721
10 transactions · 9 stateful · 2026-06-15 08:38:07 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,408,721 · 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f281f23…23e2
0x065c9d…c394
2 touches
0 conflicts
0x658ffd18…e73b
0x065c9d…c394
2 touches
0 conflicts
0x890a053a…cd3f
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xbe637a04…d6bb
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity