← previous blocknext block →recent activity
Analyzing
Block #79,406,170
10 transactions · 8 stateful · 2026-06-06 01:57:38 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,406,170 · 10 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x63c917d6…2124
0x065c9d…c394
2 touches
0 conflicts
0x660dd3f1…6bcc
0x065c9d…c394
2 touches
0 conflicts
0x742a3103…52a6
0x065c9d…c394
2 touches
0 conflicts
0xbe74e86a…eb0d
0x065c9d…c394
2 touches
0 conflicts
0xf30d4f9c…cbe4
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