← previous blocknext block →recent activity
Analyzing
Block #80,316,578
10 transactions · 5 stateful · 2026-06-10 07:19:25 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,316,578 · 10 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
0x50305812…afc8
0x065c9d…c394
4 touches
1 conflict
0x3638dd2d…1881
0x065c9d…c394
2 touches
0 conflicts
0x3de0b906…3ad9
0x065c9d…c394
2 touches
0 conflicts
0x7fa26e58…0f32
0x065c9d…c394
2 touches
0 conflicts
0xc2fd5742…3e34
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity