Block #70,995,244

← previous blocknext block →recent activity

Analyzing

Block #70,995,244

18 transactions · 14 stateful · 2026-04-28 03:01:15 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,995,244  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe670e3ec…f252

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x083a8763…5a7e

0x1b6862…e19c

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xfe1804d8…867e

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0xe670e3ec7c…08f252

← previous block·next block →recent activity