← previous blocknext block →recent activity
Analyzing
Block #80,502,014
12 transactions · 9 stateful · 2026-06-11 03:54:57 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,502,014 · 12 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
1w02w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7878e773…bad1
0x065c9d…c394
4 touches
1 conflict
0x62e5d1d8…0a93
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xb89bb749…36f5
0x065c9d…c394
2 touches
0 conflicts
0xc0c8f260…3e21
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity