← previous blocknext block →recent activity
Analyzing
Block #81,616,846
12 transactions · 8 stateful · 2026-06-16 07:44:44 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,616,846 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x860736a1…66d9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4d2a5905…6649
0x065c9d…c394
3 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xa5d7bb34…624a
0x065c9d…c394
2 touches
0 conflicts
0xe1209c86…d170
0x065c9d…c394
2 touches
0 conflicts
0xfbaf9ef0…d4d9
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 0x860736a1bf…8766d9
Audit this contract →
← previous block·next block →recent activity