Block #70,998,896

← previous blocknext block →recent activity

Analyzing

Block #70,998,896

11 transactions · 9 stateful · 2026-04-28 03:25:33 UTC

Parallelism

45/100

Blocked

56%

Avg conflicts / tx

1.27

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,998,896  ·  11 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3cf0afab…cbc8

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x131a2e…0da9

2 touches
0 conflicts

0x00000000…0002

0xb857c1…9be1

2 touches
0 conflicts

0x00000000…0004

0xd0f8a6…badc

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity