Block #71,743,141

← previous blocknext block →recent activity

Analyzing

Block #71,743,141

31 transactions · 21 stateful · 2026-05-01 14:05:40 UTC

Parallelism

81/100

Blocked

57%

Avg conflicts / tx

1.03

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,743,141  ·  31 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

0xf64d1d53…8c79

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x0be98b9f…d110

0x065c9d…c394

5 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

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 0xf64d1d53c8…868c79

← previous block·next block →recent activity