← previous blocknext block →recent activity
Analyzing
Block #70,863,703
12 transactions · 10 stateful · 2026-04-27 12:25:13 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,863,703 · 12 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
4w06w07w18w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f8d6288…bde9
0x065c9d…c394
4 touches
1 conflict
0x877d79ce…34b8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0436eca2…f152
0x065c9d…c394
4 touches
1 conflict
0x1d8c92fd…3a24
0x065c9d…c394
4 touches
1 conflict
0xd11dc26e…59ab
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
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 0x7f8d6288c8…19bde9
Audit this contract →
← previous block·next block →recent activity