← previous blocknext block →recent activity
Analyzing
Block #79,122,499
15 transactions · 13 stateful · 2026-06-04 18:22:30 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,122,499 · 15 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
1w02w13w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2784ff6…080d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x42847283…9955
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x3c5939f3…e894
0x188d58…ea8e
2 touches
0 conflicts
0x3c5939f3…e895
0x188d58…ea8e
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 0xd2784ff684…e1080d
Audit this contract →
← previous block·next block →recent activity