Block #71,557,538

← previous blocknext block →recent activity

Analyzing

Block #71,557,538

16 transactions · 11 stateful · 2026-04-30 17:30:06 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,557,538  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00f245ce…1e10

0x34b655…2a6f

4 touches
1 conflict

0x0b934e62…3eeb

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x1dc86774…166a

0x34b655…2a6f

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x5325ab6e…d421

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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 0x00f245ce7e…641e10

← previous block·next block →recent activity