← previous blocknext block →recent activity
Analyzing
Block #79,406,630
11 transactions · 9 stateful · 2026-06-06 02:00:42 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,406,630 · 11 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x228a1b1e…e34b
0x065c9d…c394
2 touches
0 conflicts
0x317d4687…bf58
0x065c9d…c394
2 touches
0 conflicts
0x3d199ec5…2c1c
0x065c9d…c394
2 touches
0 conflicts
0x76f70f64…274e
0x065c9d…c394
2 touches
0 conflicts
0xee7dbe97…b087
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity