← previous blocknext block →recent activity
Analyzing
Block #80,166,240
18 transactions · 14 stateful · 2026-06-09 14:36:52 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,166,240 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0xd466e6f9…5df3
0x065c9d…c394
2 touches
0 conflicts
0x15bddae5…7ce2
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
3 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity