Block #70,923,017

← previous blocknext block →recent activity

Analyzing

Block #70,923,017

10 transactions · 9 stateful · 2026-04-27 19:00:10 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,923,017  ·  10 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

0x24968e6d…0132

0x131a2e…0da9

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x11a41e46…f300

0x065c9d…c394

2 touches
0 conflicts

0x13bd4819…2b2a

0x065c9d…c394

2 touches
0 conflicts

0xe2e8270d…7d70

0x065c9d…c394

2 touches
0 conflicts

0xf46db129…8ff4

0x065c9d…c394

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