← previous blocknext block →recent activity
Analyzing
Block #70,878,740
18 transactions · 15 stateful · 2026-04-27 14:05:23 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,878,740 · 18 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
3w04w16w08w111w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd843af4c…1804
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0x0c9bde9a…352a
0x065c9d…c394
6 touches
3 conflicts
0x1c008196…71f5
0x065c9d…c394
6 touches
3 conflicts
0x86736d6c…dca9
0x065c9d…c394
6 touches
3 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
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 0xd843af4cf7…f41804
Audit this contract →
← previous block·next block →recent activity