← previous blocknext block →recent activity
Analyzing
Block #80,226,664
15 transactions · 12 stateful · 2026-06-09 21:19:44 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,226,664 · 15 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x87c1fa6b…55b5
0x065c9d…c394
3 touches
1 conflict
0xac21fef6…0d12
0x065c9d…c394
3 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x34dcc028…bd74
0x065c9d…c394
2 touches
0 conflicts
0x5c3c767d…e234
0x065c9d…c394
2 touches
0 conflicts
0xe5b79fcb…d1bc
0x1efe02…37d6
2 touches
0 conflicts
0x5cab5bda…798b
0x2880ab…7b43
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