Block #70,956,782

← previous blocknext block →recent activity

Analyzing

Block #70,956,782

14 transactions · 13 stateful · 2026-04-27 22:44:57 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,956,782  ·  14 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

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x2d2b8493…6045

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x737675b5…575d

0x34b655…2a6f

2 touches
0 conflicts

0x7b5b808e…f99b

0x34b655…2a6f

2 touches
0 conflicts

0x8aa1941d…2988

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 0x85a88798de…47f85e

← previous block·next block →recent activity