← previous blocknext block →recent activity
Analyzing
Block #80,256,570
23 transactions · 20 stateful · 2026-06-10 00:39:18 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,256,570 · 23 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
2w04w05w16w07w28w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x681a4c8a…d8cd
0x065c9d…c394
3 touches
1 conflict
0x98ea7a2c…9f62
0xd32edf…ff58
3 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
3 touches
1 conflict
0xfe3bddd2…8b48
0x3bd359…433a
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity