← previous blocknext block →recent activity
Analyzing
Block #80,653,082
13 transactions · 12 stateful · 2026-06-11 20:43:27 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,653,082 · 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xa3a5b782…aca6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x0f67a283…68d2
0x40c49f…2af0
2 touches
0 conflicts
0x53745efe…77aa
0x40c49f…2af0
2 touches
0 conflicts
0xe875cb1f…0e2e
0x40c49f…2af0
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: MarginAccount
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity