Block #70,908,852

← previous blocknext block →recent activity

Analyzing

Block #70,908,852

15 transactions · 13 stateful · 2026-04-27 17:25:51 UTC

Parallelism

67/100

Blocked

31%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

4 touches
1 conflict

0x3ac9e0f2…b632

0x34b655…2a6f

4 touches
1 conflict

0x6f2e60dc…e661

0x34b655…2a6f

4 touches
1 conflict

0x7b50a82b…f53d

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity