Block #70,996,562

← previous blocknext block →recent activity

Analyzing

Block #70,996,562

34 transactions · 25 stateful · 2026-04-28 03:10:02 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,996,562  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x131a2e…0da9

4 touches
1 conflict

0x0c05ae63…f1f2

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity