← previous blocknext block →recent activity

Analyzing

Block #71,450,066

28 transactions · 27 stateful · 2026-04-30 05:30:26 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

1.68

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,450,066  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x451e482b…7e7d

0x34b655…2a6f

10 touches
10 conflicts

0x21d6593f…26e1

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x4284233f…5bde

0xd32edf…ff58

7 touches
6 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 0x451e482b59…427e7d

← previous block·next block →recent activity