Block #70,878,033

← previous blocknext block →recent activity

Analyzing

Block #70,878,033

17 transactions · 12 stateful · 2026-04-27 14:00:40 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,878,033  ·  17 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

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…0001

0xc1a578…8e1a

4 touches
1 conflict

0x6168aa33…a527

0x065c9d…c394

3 touches
1 conflict

0xd644c6c6…eb3f

0x065c9d…c394

3 touches
1 conflict

0x09000000…0001

0x000000…1000

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