Block #71,702,080

← previous blocknext block →recent activity

Analyzing

Block #71,702,080

14 transactions · 11 stateful · 2026-05-01 09:32:11 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,702,080  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xed10a2fb…429d

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x4e3b7eca…d3c0

0x065c9d…c394

5 touches
3 conflicts

0x03d3105e…ba5a

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

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

6 conflicts on slot 0xed10a2fbe4…68429d

← previous block·next block →recent activity