← previous blocknext block →recent activity
Analyzing
Block #79,021,367
15 transactions · 11 stateful · 2026-06-04 07:08:04 UTC
Parallelism
80/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,021,367 · 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x752fee2e…af42
0x065c9d…c394
3 touches
1 conflict
0xb762a84b…734e
0x065c9d…c394
3 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x6debcaad…6e57
0x065c9d…c394
2 touches
0 conflicts
0x976837e3…2bd4
0x065c9d…c394
2 touches
0 conflicts
0x9aaf976c…788d
0x065c9d…c394
2 touches
0 conflicts
0x9c605c9f…cb62
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