Block #70,918,044

← previous blocknext block →recent activity

Analyzing

Block #70,918,044

13 transactions · 11 stateful · 2026-04-27 18:27:07 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,918,044  ·  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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x24968e6d…0132

0x131a2e…0da9

3 touches
1 conflict

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x1ab8d497…6888

0x73ada1…8be0

2 touches
0 conflicts

0x5365a8f4…fb48

0x73ada1…8be0

2 touches
0 conflicts

0x85f06b95…c2d9

0x73ada1…8be0

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity