← previous blocknext block →recent activity
Analyzing
Block #80,823,387
17 transactions · 14 stateful · 2026-06-12 15:38:54 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,823,387 · 17 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
2w03w04w110w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6b917f…3a72
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x32edb416…e298
0x5afd3e…7620
2 touches
0 conflicts
0x3ad0fc58…9efd
0x5afd3e…7620
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-WETH/USDC
1 conflict on slot 0xde6b917faa…a83a72
Audit this contract →
← previous block·next block →recent activity