Block #71,704,075

← previous blocknext block →recent activity

Analyzing

Block #71,704,075

11 transactions · 9 stateful · 2026-05-01 09:45:28 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,704,075  ·  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

0x6bb22c06…c9de

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x24c678a4…d574

0x1001ff…1001

2 touches
0 conflicts

0xc6f1b3af…c97c

0x1001ff…1001

2 touches
0 conflicts

0xf60bb017…fc20

0x188d58…ea8e

2 touches
0 conflicts

0xf60bb017…fc22

0x188d58…ea8e

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 0x6bb22c066e…fec9de

← previous block·next block →recent activity