Block #70,951,384

← previous blocknext block →recent activity

Analyzing

Block #70,951,384

13 transactions · 12 stateful · 2026-04-27 22:09:01 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,951,384  ·  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

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0xdf671536…aa02

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x764f2d09…bc43

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 0x414e9446b2…294b59

← previous block·next block →recent activity