← previous blocknext block →recent activity
Analyzing
Block #80,290,984
14 transactions · 10 stateful · 2026-06-10 04:28:44 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,290,984 · 14 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
2w03w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x16599d5b…9164
0x065c9d…c394
2 touches
0 conflicts
0x26b30f36…ec4e
0x065c9d…c394
2 touches
0 conflicts
0x3ad572e2…37d9
0x065c9d…c394
2 touches
0 conflicts
0x6d32d085…9ffe
0x065c9d…c394
2 touches
0 conflicts
0xa85d5ef3…4cd3
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity