Block #70,918,071

← previous blocknext block →recent activity

Analyzing

Block #70,918,071

6 transactions · 6 stateful · 2026-04-27 18:27:18 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,918,071  ·  6 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

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0x107c73c0…b43b

0xd32edf…ff58

3 touches
1 conflict

0x0dbf9688…c6cf

0x10aeaf…5417

2 touches
0 conflicts

0xad8e2502…0464

0x10aeaf…5417

2 touches
0 conflicts

0x36cd3056…b5d4

0x188d58…ea8e

2 touches
0 conflicts

0x36cd3056…b5d5

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…00001d

← previous block·next block →recent activity