Block #71,744,217

← previous blocknext block →recent activity

Analyzing

Block #71,744,217

25 transactions · 20 stateful · 2026-05-01 14:12:51 UTC

Parallelism

76/100

Blocked

55%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,744,217  ·  25 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

0x00000000…0002

0x7e9d3a…9fda

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0xfbabb02d…af07

0x34b655…2a6f

4 touches
1 conflict

0x44279a41…1f43

0xa6afd3…d132

3 touches
1 conflict

0x3e598780…1d5e

0xd32edf…ff58

3 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

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: 0x7e9d3a8a…4f9fda

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity