Block #70,908,418

← previous blocknext block →recent activity

Analyzing

Block #70,908,418

12 transactions · 12 stateful · 2026-04-27 17:22:59 UTC

Parallelism

83/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,908,418  ·  12 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

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x1cd10083…3b65

0x065c9d…c394

3 touches
1 conflict

0x5486a1ba…581d

0x065c9d…c394

3 touches
1 conflict

0xa76f5d2d…4379

0x065c9d…c394

3 touches
1 conflict

0xac03342e…cdc2

0x065c9d…c394

3 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

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