Block #71,448,840

← previous blocknext block →recent activity

Analyzing

Block #71,448,840

19 transactions · 15 stateful · 2026-04-30 05:22:15 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,448,840  ·  19 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

0x8558628a…56e2

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x5a3732cb…edb3

0x1b6862…e19c

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x11e1e2a4…54fb

0x34b655…2a6f

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

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

15 conflicts on slot 0x8558628a20…1656e2

← previous block·next block →recent activity