Block #70,892,413

← previous blocknext block →recent activity

Analyzing

Block #70,892,413

16 transactions · 15 stateful · 2026-04-27 15:36:22 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,892,413  ·  16 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

0x2978990f…df25

0x065c9d…c394

6 touches
3 conflicts

0x5f5a65a8…3acc

0x065c9d…c394

6 touches
3 conflicts

0x630ccf4b…7a9d

0x065c9d…c394

6 touches
3 conflicts

0xca3463bb…9398

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x03b0a012…746d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 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 0x2978990f72…c6df25

← previous block·next block →recent activity