Block #71,037,219

← previous blocknext block →recent activity

Analyzing

Block #71,037,219

29 transactions · 25 stateful · 2026-04-28 07:40:37 UTC

Parallelism

79/100

Blocked

56%

Avg conflicts / tx

0.97

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,037,219  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x703751bc…6df2

0xd32edf…ff58

11 touches
15 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xdbc6e634…e16c

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: 0xd32edf66…9fff58

15 conflicts on slot 0x703751bcec…446df2

← previous block·next block →recent activity