Block #70,998,563

← previous blocknext block →recent activity

Analyzing

Block #70,998,563

13 transactions · 10 stateful · 2026-04-28 03:23:21 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,998,563  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x03d109e4…5f1f

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d4cc8b9…d76e

0x065c9d…c394

3 touches
1 conflict

0x526febd7…86ac

0x065c9d…c394

3 touches
1 conflict

0x8d44d1e7…4f0e

0x065c9d…c394

3 touches
1 conflict

0x3638e1ad…ec0e

0x34b655…2a6f

2 touches
0 conflicts

0x578e7f66…1b56

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

1 conflict on slot 0x03d109e4dc…985f1f

← previous block·next block →recent activity