← previous blocknext block →recent activity
Analyzing
Block #80,821,743
14 transactions · 11 stateful · 2026-06-12 15:27:56 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,821,743 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06fa2f2e…b0c1
0xd32edf…ff58
3 touches
1 conflict
0x064addc5…d5d4
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x68ddc645…f0a2
0x065c9d…c394
2 touches
0 conflicts
0xc2db86f1…6f8a
0x065c9d…c394
2 touches
0 conflicts
0xd0c5efcd…d762
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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