← previous blocknext block →recent activity
Analyzing
Block #80,465,704
13 transactions · 11 stateful · 2026-06-10 23:53:06 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,465,704 · 13 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
1w03w14w05w26w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3418c11a…4bb2
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
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 0x3418c11a66…464bb2
Audit this contract →
← previous block·next block →recent activity