Block #71,555,722

← previous blocknext block →recent activity

Analyzing

Block #71,555,722

10 transactions · 8 stateful · 2026-04-30 17:18:00 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,555,722  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x2557abf8…2901

0x34b655…2a6f

2 touches
0 conflicts

0x8a5efe9a…fa31

0x34b655…2a6f

2 touches
0 conflicts

0xcbbdfdfd…be59

0x34b655…2a6f

2 touches
0 conflicts

0xd16b2bcc…76b6

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x4f4bdabdf3…ecffba

← previous block·next block →recent activity