← previous blocknext block →recent activity
Analyzing
Block #80,265,112
14 transactions · 10 stateful · 2026-06-10 01:36:17 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,265,112 · 14 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1e7886…a232
0x065c9d…c394
4 touches
1 conflict
0x601ca1e6…e99b
0x065c9d…c394
4 touches
1 conflict
0xfddbdd16…29ad
0x065c9d…c394
3 touches
1 conflict
0x12d584ae…9a78
0x065c9d…c394
3 touches
1 conflict
0x5c90438d…1a41
0x065c9d…c394
3 touches
1 conflict
0x93d4cff9…829d
0x065c9d…c394
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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 0x5d1e7886a6…2ca232
Audit this contract →
← previous block·next block →recent activity