Block #71,743,875

← previous blocknext block →recent activity

Analyzing

Block #71,743,875

14 transactions · 12 stateful · 2026-05-01 14:10:34 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,743,875  ·  14 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

0x36e305d5…aa7e

0xd32edf…ff58

11 touches
15 conflicts

0xd5b10148…e636

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3ffd5ba2…8225

0x065c9d…c394

4 touches
1 conflict

0x8cb4260e…2ff5

0x065c9d…c394

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 0x36e305d58e…1eaa7e

← previous block·next block →recent activity