Block #70,923,048

← previous blocknext block →recent activity

Analyzing

Block #70,923,048

14 transactions · 10 stateful · 2026-04-27 19:00:23 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,923,048  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x15ef009d…3eec

0x065c9d…c394

6 touches
3 conflicts

0x3cd4bd2b…419d

0x065c9d…c394

6 touches
3 conflicts

0x68cf2bad…bd95

0x065c9d…c394

6 touches
3 conflicts

0xa5b4c9e6…2410

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x5c05221b…b62a

0xd32edf…ff58

3 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity