← previous blocknext block →recent activity
Analyzing
Block #79,418,587
20 transactions · 18 stateful · 2026-06-06 03:20:25 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,418,587 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x6b8d5e1f…be83
0x065c9d…c394
4 touches
1 conflict
0x0d2f63c9…5724
0x065c9d…c394
2 touches
0 conflicts
0x2b945c8a…49a1
0x065c9d…c394
2 touches
0 conflicts
0x8b3c32e4…a683
0x065c9d…c394
2 touches
0 conflicts
0xa42b58c9…2dd5
0x065c9d…c394
2 touches
0 conflicts
0xf2b1dd5c…3930
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