← previous blocknext block →recent activity

Analyzing

Block #71,283,877

26 transactions · 22 stateful · 2026-04-29 11:02:42 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,283,877  ·  26 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

0x801a6e57…d85c

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0001

0xc1a578…8e1a

8 touches
6 conflicts

0x00000000…0000

0xc1a578…8e1a

8 touches
6 conflicts

0x150af51d…9c42

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x3e0f56fb…e78f

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

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 0x801a6e5726…c1d85c

← previous block·next block →recent activity