Block #70,996,303

← previous blocknext block →recent activity

Analyzing

Block #70,996,303

13 transactions · 12 stateful · 2026-04-28 03:08:18 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,996,303  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x518100e6…64e8

0x065c9d…c394

3 touches
1 conflict

0xae0b7534…f7db

0x065c9d…c394

3 touches
1 conflict

0xe0c7d7b4…99de

0x065c9d…c394

3 touches
1 conflict

0xf1c6599c…6596

0x065c9d…c394

3 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity