← previous blocknext block →recent activity
Analyzing
Block #80,937,026
8 transactions · 8 stateful · 2026-06-13 04:16:46 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,937,026 · 8 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5e91e9b9…aa01
0x065c9d…c394
4 touches
1 conflict
0x8974b93b…0ff6
0x065c9d…c394
3 touches
1 conflict
0x90a8c04f…70e9
0x065c9d…c394
3 touches
1 conflict
0x429e8b27…806f
0x34b655…2a6f
2 touches
0 conflicts
0x496ff651…1310
0x34b655…2a6f
2 touches
0 conflicts
0x781f5487…d318
0x34b655…2a6f
2 touches
0 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
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