← previous blocknext block →recent activity
Analyzing
Block #70,999,242
9 transactions · 8 stateful · 2026-04-28 03:27:48 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,999,242 · 9 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
0xea228ba8…3a1d
0x065c9d…c394
6 touches
3 conflicts
0x2910e444…562c
0x065c9d…c394
6 touches
3 conflicts
0x2a24d18a…56c1
0x065c9d…c394
6 touches
3 conflicts
0x6518c685…7c09
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0xc0561122…4fcf
0x065c9d…c394
6 touches
3 conflicts
0x1c68aeca…2e22
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
3 conflicts on slot 0xea228ba821…4b3a1d
Audit this contract →
← previous block·next block →recent activity