← previous blocknext block →recent activity
Analyzing
Block #79,417,469
15 transactions · 12 stateful · 2026-06-06 03:12:57 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,417,469 · 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
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xad31f013…3006
0x065c9d…c394
2 touches
0 conflicts
0xc0c767ef…cf67
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0070
0x1efe02…37d6
2 touches
0 conflicts
0x384ce8e6…8bc7
0x1efe02…37d6
2 touches
0 conflicts
0xf6d5644f…b9f7
0x1efe02…37d6
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