← previous blocknext block →recent activity
Analyzing
Block #79,414,034
12 transactions · 11 stateful · 2026-06-06 02:50:04 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,414,034 · 12 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x0f77d101…a4c0
0x065c9d…c394
2 touches
0 conflicts
0x43aede37…4fb3
0x065c9d…c394
2 touches
0 conflicts
0xd21337e4…d04d
0x065c9d…c394
2 touches
0 conflicts
0xd7da0202…65cf
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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