Block #71,416,692

← previous blocknext block →recent activity

Analyzing

Block #71,416,692

17 transactions · 17 stateful · 2026-04-30 01:48:04 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.18

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,416,692  ·  17 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

0x676f9f01…a8ac

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0dd5cdfa…574f

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

6 touches
3 conflicts

0x30c10c87…22ec

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x3b74ae43…a235

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

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: 0x34b6552d…112a6f

10 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity