← previous blocknext block →recent activity
Analyzing
Block #80,328,105
16 transactions · 13 stateful · 2026-06-10 08:36:15 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,328,105 · 16 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
1w02w13w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc808718a…fb48
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xd8d828a7…b649
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x158accef…4c74
0xa6afd3…d132
4 touches
1 conflict
0xe41f8863…29a4
0xa6afd3…d132
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
1 conflict on slot 0xc808718a77…6ffb48
Audit this contract →
← previous block·next block →recent activity