← previous blocknext block →recent activity
Analyzing
Block #70,845,618
8 transactions · 7 stateful · 2026-04-27 10:24:44 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,845,618 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63afb3d2…53d9
0x065c9d…c394
4 touches
1 conflict
0xc2de4b5b…dae7
0x065c9d…c394
4 touches
1 conflict
0xf844a826…7dae
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4f2c660c…5502
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c2
0x1b6862…e19c
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 0x63afb3d220…5c53d9
Audit this contract →
← previous block·next block →recent activity