Block #70,877,842

← previous blocknext block →recent activity

Analyzing

Block #70,877,842

7 transactions · 6 stateful · 2026-04-27 13:59:24 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,842  ·  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

0xb640613b…3191

0x065c9d…c394

4 touches
1 conflict

0xdde562d7…885c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x004390c5…3059

0x065c9d…c394

4 touches
1 conflict

0x1f4e63c1…8ebc

0x065c9d…c394

4 touches
1 conflict

0x29d84570…99a5

0x065c9d…c394

2 touches
1 conflict

0x29d84570…99a6

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 0xb640613b80…c23191

← previous block·next block →recent activity