← previous blocknext block →recent activity
Analyzing
Block #80,473,580
13 transactions · 12 stateful · 2026-06-11 00:45:34 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,473,580 · 13 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
1w03w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x8650d03b…a3fd
0x065c9d…c394
2 touches
0 conflicts
0x9a998a18…da43
0x065c9d…c394
2 touches
0 conflicts
0xd357f6b7…a423
0x065c9d…c394
2 touches
0 conflicts
0xeca0ca60…4117
0x065c9d…c394
2 touches
0 conflicts
0xf08b04d4…6f31
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity