Block #70,846,252

← previous blocknext block →recent activity

Analyzing

Block #70,846,252

10 transactions · 9 stateful · 2026-04-27 10:28:56 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,846,252  ·  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

0x51c4de47…c4a3

0x065c9d…c394

4 touches
1 conflict

0x5b8f4372…abdd

0x065c9d…c394

4 touches
1 conflict

0x1d14eccb…a003

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x483bdaf1…9aee

0x065c9d…c394

4 touches
1 conflict

0x8a1cc272…e8cd

0x065c9d…c394

2 touches
1 conflict

0x9abd9ca4…ff66

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 0x51c4de4731…01c4a3

← previous block·next block →recent activity