Block #71,420,816

← previous blocknext block →recent activity

Analyzing

Block #71,420,816

13 transactions · 11 stateful · 2026-04-30 02:15:25 UTC

Parallelism

62/100

Blocked

55%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,420,816  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xde8c6922…913a

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x0a85a226…83c1

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0xe28c84d7…58fe

0xd32edf…ff58

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

6 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity