Block #71,445,911

← previous blocknext block →recent activity

Analyzing

Block #71,445,911

10 transactions · 8 stateful · 2026-04-30 05:02:45 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,445,911  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x468c69b1…af11

0x8d66a4…3095

3 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

3 touches
1 conflict

0x90ecce76…8a38

0x1efe02…37d6

2 touches
0 conflicts

0x1728ed63…499c

0xea1b8e…c5ec

2 touches
0 conflicts

0x3026b11b…77d4

0xea1b8e…c5ec

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x567cd154…b1c8

0xea1b8e…c5ec

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity