← previous blocknext block →recent activity
Analyzing
Block #80,745,975
24 transactions · 21 stateful · 2026-06-12 07:02:47 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,745,975 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w39w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x89d45d08…41ac
0x065c9d…c394
4 touches
1 conflict
0x2d311bb6…4a09
0x065c9d…c394
3 touches
1 conflict
0xc826d5f0…550c
0x065c9d…c394
3 touches
1 conflict
0x3e247b94…fd7c
0x754704…b603
2 touches
0 conflicts
0xa060b594…669d
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity