← previous blocknext block →recent activity
Analyzing
Block #80,257,101
13 transactions · 10 stateful · 2026-06-10 00:42:50 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,257,101 · 13 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
1w03w15w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0a338c30…5fe4
0x065c9d…c394
2 touches
0 conflicts
0x27192370…7bd1
0x065c9d…c394
2 touches
0 conflicts
0x63cf246c…21c9
0x065c9d…c394
2 touches
0 conflicts
0xc4cc34b0…93b9
0x065c9d…c394
2 touches
0 conflicts
0xdcfb4376…b169
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