Block #70,995,165

← previous blocknext block →recent activity

Analyzing

Block #70,995,165

10 transactions · 9 stateful · 2026-04-28 03:00:44 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x449de693…e03c

0x065c9d…c394

3 touches
1 conflict

0x43c08d10…827d

0x065c9d…c394

3 touches
1 conflict

0x4137d3e7…f03d

0x065c9d…c394

2 touches
1 conflict

0x4f28e9af…9d33

0x065c9d…c394

2 touches
1 conflict

0x4f28e9af…9d34

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 0x0000000000…00003d

← previous block·next block →recent activity