Block #70,995,008

← previous blocknext block →recent activity

Analyzing

Block #70,995,008

7 transactions · 7 stateful · 2026-04-28 02:59:41 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,995,008  ·  7 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

0xf86300c2…ad42

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xb17dc62e…919e

0x065c9d…c394

4 touches
1 conflict

0x0de2af44…1710

0x065c9d…c394

2 touches
1 conflict

0x59eed5a4…4896

0x065c9d…c394

2 touches
1 conflict

0x59eed5a4…4897

0x065c9d…c394

2 touches
1 conflict

0x0de2af44…1711

0x065c9d…c394

2 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

1 conflict on slot 0xf86300c24d…9bad42

← previous block·next block →recent activity