← previous blocknext block →recent activity
Analyzing
Block #80,234,508
19 transactions · 11 stateful · 2026-06-09 22:12:19 UTC
Parallelism
89/100
Blocked
9%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,234,508 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b4018d6…d143
0x065c9d…c394
2 touches
0 conflicts
0xa96d7054…5a4a
0x065c9d…c394
2 touches
0 conflicts
0xb76b2d2c…975c
0x065c9d…c394
2 touches
0 conflicts
0xc2afc7c0…c816
0x065c9d…c394
2 touches
0 conflicts
0xe748b9ea…f3e6
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity