Block #71,449,628

← previous blocknext block →recent activity

Analyzing

Block #71,449,628

13 transactions · 13 stateful · 2026-04-30 05:27:31 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,449,628  ·  13 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

0x1da1c6cb…bb3f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5b645d44…28c2

0x1efe02…37d6

2 touches
0 conflicts

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x15f59c70…2918

0x73ada1…8be0

2 touches
0 conflicts

0x512fb0d4…9b6f

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42f7

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42fa

0x73ada1…8be0

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 0x1da1c6cbeb…31bb3f

← previous block·next block →recent activity