← previous blocknext block →recent activity
Analyzing
Block #80,823,551
18 transactions · 16 stateful · 2026-06-12 15:40:00 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,823,551 · 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
1w02w14w05w16w17w28w010w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4efa90b3…d307
0x754704…b603
4 touches
1 conflict
0x00000000…000c
0x5e5e5f…7924
4 touches
1 conflict
0x00000000…0004
0x5e5e5f…7924
4 touches
1 conflict
0xaa625301…4537
0x000000…012a
4 touches
1 conflict
0x00000000…0002
0x5e5e5f…7924
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
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