← previous blocknext block →recent activity
Analyzing
Block #70,923,391
13 transactions · 12 stateful · 2026-04-27 19:02:39 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,923,391 · 13 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
3w04w18w09w010w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x74d91a2c…8e2f
0x065c9d…c394
4 touches
1 conflict
0xa0281eb2…a303
0x065c9d…c394
4 touches
1 conflict
0xe1a930e8…77df
0x065c9d…c394
4 touches
1 conflict
0xe23556df…ffe5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
4 touches
1 conflict
0xbbee74c2…567a
0x131a2e…0da9
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity