Block #71,683,801

← previous blocknext block →recent activity

Analyzing

Block #71,683,801

6 transactions · 6 stateful · 2026-05-01 07:30:30 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,683,801  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1ec9eac3…f6cb

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xec19b8f5…12ee

0x065c9d…c394

4 touches
1 conflict

0x4124e0a8…0e78

0x065c9d…c394

3 touches
1 conflict

0xd2ce2345…f1e2

0x065c9d…c394

3 touches
1 conflict

0x4b654a09…4912

0x065c9d…c394

3 touches
1 conflict

0xbcd06717…bfb7

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

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: 0x065c9d28…a9c394

1 conflict on slot 0x1ec9eac30c…c9f6cb

← previous block·next block →recent activity