← previous blocknext block →recent activity
Analyzing
Block #70,846,672
12 transactions · 12 stateful · 2026-04-27 10:31:44 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,846,672 · 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59fd9be8…93d0
0x065c9d…c394
4 touches
1 conflict
0xb587d3e0…b2c3
0x065c9d…c394
4 touches
1 conflict
0xc71e61ce…1eae
0x065c9d…c394
4 touches
1 conflict
0xecb9a3d3…3bdd
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
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 0x59fd9be800…c493d0
Audit this contract →
← previous block·next block →recent activity