← previous blocknext block →recent activity

Analyzing

Block #70,892,540

18 transactions · 17 stateful · 2026-04-27 15:37:13 UTC

Parallelism

89/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,892,540  ·  18 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

0x1cc305d6…f278

0x065c9d…c394

4 touches
1 conflict

0x258a9d43…4202

0x065c9d…c394

4 touches
1 conflict

0x214dc988…ba27

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

4 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