← previous blocknext block →recent activity
Analyzing
Block #70,863,486
10 transactions · 8 stateful · 2026-04-27 12:23:46 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,863,486 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c50c38…7a74
0x065c9d…c394
6 touches
3 conflicts
0x0abedc7e…a5f7
0x065c9d…c394
6 touches
3 conflicts
0x63be7197…b90f
0x065c9d…c394
6 touches
3 conflicts
0xcc8305ba…86bc
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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
3 conflicts on slot 0x06c50c384f…f07a74
Audit this contract →
← previous block·next block →recent activity