← previous blocknext block →recent activity
Analyzing
Block #70,911,799
11 transactions · 10 stateful · 2026-04-27 17:45:29 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,911,799 · 11 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663c86e9…d6fb
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xfc2930e7…ffd8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2eaa658b…4dd5
0x065c9d…c394
4 touches
1 conflict
0x40bd31d0…c652
0x065c9d…c394
4 touches
1 conflict
0xd352f74e…8006
0x065c9d…c394
2 touches
1 conflict
0x72313b18…9fe8
0x065c9d…c394
2 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 0x663c86e934…74d6fb
Audit this contract →
← previous block·next block →recent activity