Block #70,908,622

← previous blocknext block →recent activity

Analyzing

Block #70,908,622

14 transactions · 14 stateful · 2026-04-27 17:24:20 UTC

Parallelism

64/100

Blocked

29%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,908,622  ·  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

0xcfdef5a3…28bb

0x065c9d…c394

9 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x58e06bab…34d0

0x1b6862…e19c

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

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: 0x065c9d28…a9c394

10 conflicts on slot 0xcfdef5a3da…6328bb

← previous block·next block →recent activity