← previous blocknext block →recent activity
Analyzing
Block #70,923,368
7 transactions · 7 stateful · 2026-04-27 19:02:30 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,923,368 · 7 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
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1f99b36c…aa96
0x065c9d…c394
2 touches
0 conflicts
0x5125c123…d419
0x065c9d…c394
2 touches
0 conflicts
0x6e2b2f4b…558c
0x065c9d…c394
2 touches
0 conflicts
0x6fe133de…05bb
0x065c9d…c394
2 touches
0 conflicts
0x9cab6d89…f727
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
1 conflict on slot 0xbbee74c2e7…6e567a
Audit this contract →
← previous block·next block →recent activity