Block #70,981,909

← previous blocknext block →recent activity

Analyzing

Block #70,981,909

8 transactions · 7 stateful · 2026-04-28 01:32:26 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,981,909  ·  8 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

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xecd87a39…d9c5

0x34b655…2a6f

4 touches
1 conflict

0x2578f3dc…b3d7

0x2a68ba…90c5

2 touches
0 conflicts

0x50910633…5225

0x2a68ba…90c5

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x01737532…9b12

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

1 conflict on slot 0x9e719c7aca…c7df63

← previous block·next block →recent activity