← previous blocknext block →recent activity
Analyzing
Block #80,270,514
15 transactions · 12 stateful · 2026-06-10 02:12:15 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,270,514 · 15 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
1w02w13w24w25w16w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x672b3924…b103
0x065c9d…c394
3 touches
1 conflict
0xf60bb017…fc20
0x188d58…ea8e
2 touches
0 conflicts
0xf60bb017…fc22
0x188d58…ea8e
2 touches
0 conflicts
0xf60bb017…fc23
0x188d58…ea8e
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