Block #70,911,069

← previous blocknext block →recent activity

Analyzing

Block #70,911,069

13 transactions · 12 stateful · 2026-04-27 17:40:37 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,911,069  ·  13 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

0x2206edf4…8d6e

0x065c9d…c394

4 touches
1 conflict

0x5c041856…00d4

0x065c9d…c394

4 touches
1 conflict

0x7213acb3…f04c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xed31adac…46cc

0x065c9d…c394

4 touches
1 conflict

0x85f1b45a…db6e

0x065c9d…c394

2 touches
1 conflict

0x08e0bf95…3778

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 0x2206edf447…248d6e

← previous block·next block →recent activity