Block #71,789,192

← previous blocknext block →recent activity

Analyzing

Block #71,789,192

11 transactions · 11 stateful · 2026-05-01 19:12:44 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,789,192  ·  11 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

0x8b41ec8f…c2d9

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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: 0x1b68626d…2de19c

1 conflict on slot 0x8b41ec8f85…dbc2d9

← previous block·next block →recent activity