Block #70,911,409

← previous blocknext block →recent activity

Analyzing

Block #70,911,409

10 transactions · 8 stateful · 2026-04-27 17:42:53 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,911,409  ·  10 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

0x0b2e26cc…4565

0x065c9d…c394

4 touches
1 conflict

0x3d22b07d…0d78

0x065c9d…c394

4 touches
1 conflict

0x8f127916…d9f6

0x065c9d…c394

4 touches
1 conflict

0xb0bc13aa…fb67

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3aa3322a…25a4

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

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 0x0b2e26cc80…324565

← previous block·next block →recent activity