Block #70,878,008

← previous blocknext block →recent activity

Analyzing

Block #70,878,008

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

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,878,008  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2f9e01e1…e43e

0x065c9d…c394

4 touches
1 conflict

0x4bc881d3…03c8

0x065c9d…c394

4 touches
1 conflict

0x50eb7faf…0b78

0x065c9d…c394

4 touches
1 conflict

0xf8e87842…51f7

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xd11dc26e…59ab

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity