← previous blocknext block →recent activity
Analyzing
Block #80,330,298
19 transactions · 15 stateful · 2026-06-10 08:50:50 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,330,298 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x6685789a…d441
0x065c9d…c394
2 touches
0 conflicts
0x776da878…2464
0x065c9d…c394
2 touches
0 conflicts
0xac4ff825…e46e
0x065c9d…c394
2 touches
0 conflicts
0xb5e6e979…e6a3
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
1 conflict on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity