Block #71,449,652

← previous blocknext block →recent activity

Analyzing

Block #71,449,652

10 transactions · 8 stateful · 2026-04-30 05:27:40 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,449,652  ·  10 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

0x37d49489…9309

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x5d8373b9…233d

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233e

0x44b60b…f711

2 touches
0 conflicts

0x5d8373b9…233f

0x44b60b…f711

2 touches
0 conflicts

0x8956cb26…42f7

0x44b60b…f711

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 0x37d494895c…549309

← previous block·next block →recent activity