← previous blocknext block →recent activity
Analyzing
Block #79,419,639
15 transactions · 14 stateful · 2026-06-06 03:27:25 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,419,639 · 15 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
1w02w13w04w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f054385…21f6
0x065c9d…c394
6 touches
3 conflicts
0xde6f5406…2bad
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0120f4d7…23d6
0x065c9d…c394
3 touches
1 conflict
0x47d01be1…d9e8
0x065c9d…c394
3 touches
1 conflict
0x6b449bd6…d98c
0x065c9d…c394
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
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
3 conflicts on slot 0x7f054385dd…f621f6
Audit this contract →
← previous block·next block →recent activity