Block #70,956,800

← previous blocknext block →recent activity

Analyzing

Block #70,956,800

14 transactions · 11 stateful · 2026-04-27 22:45:04 UTC

Parallelism

64/100

Blocked

55%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,956,800  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe80f9a5d…f6c4

0xd32edf…ff58

9 touches
10 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

0x1179284b…db76

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: 0xd32edf66…9fff58

10 conflicts on slot 0xe80f9a5da3…5af6c4

← previous block·next block →recent activity