Block #71,555,923

← previous blocknext block →recent activity

Analyzing

Block #71,555,923

7 transactions · 6 stateful · 2026-04-30 17:19:21 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,555,923  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xff5c097d…680c

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x78ac2377…804c

0x0dfbc6…7777

2 touches
0 conflicts

0x8fa7a69c…8fd7

0x0dfbc6…7777

2 touches
0 conflicts

0xb96e29a5…0419

0x34b655…2a6f

2 touches
0 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

2 touches
0 conflicts

0x536e2740…61ac

0x3bd359…433a

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 0xff5c097d54…35680c

← previous block·next block →recent activity