Block #70,981,530

← previous blocknext block →recent activity

Analyzing

Block #70,981,530

13 transactions · 12 stateful · 2026-04-28 01:29:55 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,981,530  ·  13 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x0659fa0f…fd59

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x26bbcb47…263f

0x34b655…2a6f

2 touches
0 conflicts

0x47dc50d5…5d8b

0x34b655…2a6f

2 touches
0 conflicts

0x5ff45b64…6556

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity