Block #71,449,178

← previous blocknext block →recent activity

Analyzing

Block #71,449,178

11 transactions · 9 stateful · 2026-04-30 05:24:31 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,449,178  ·  11 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x2af15229…c0df

0x065c9d…c394

3 touches
1 conflict

0x00000000…0005

0x2a3755…a5a6

2 touches
0 conflicts

0xd5daadcc…c9b9

0x2a3755…a5a6

2 touches
0 conflicts

0xe870e232…7369

0x2a3755…a5a6

2 touches
0 conflicts

0x11e1e2a4…54fb

0x34b655…2a6f

2 touches
0 conflicts

0x23114fac…630a

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity