Block #70,995,347

← previous blocknext block →recent activity

Analyzing

Block #70,995,347

13 transactions · 12 stateful · 2026-04-28 03:01:56 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,995,347  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x131a2e…0da9

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002e

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c5

0x1b6862…e19c

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity