Block #70,923,163

← previous blocknext block →recent activity

Analyzing

Block #70,923,163

7 transactions · 5 stateful · 2026-04-27 19:01:09 UTC

Parallelism

57/100

Blocked

40%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,923,163  ·  7 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

0x8140da28…f56c

0x065c9d…c394

6 touches
3 conflicts

0xac03342e…cdc2

0x065c9d…c394

6 touches
3 conflicts

0x0aad3b27…67d8

0x065c9d…c394

6 touches
3 conflicts

0xc464fce7…dbac

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6fe133de…05bb

0x065c9d…c394

6 touches
3 conflicts

0xb723df31…16e7

0x065c9d…c394

2 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

3 conflicts on slot 0x8140da28dd…eff56c

← previous block·next block →recent activity