Block #71,683,767

← previous blocknext block →recent activity

Analyzing

Block #71,683,767

6 transactions · 6 stateful · 2026-05-01 07:30:17 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,767  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xec19b8f5…12ee

0x065c9d…c394

4 touches
1 conflict

0x1ec9eac3…f6cb

0x065c9d…c394

4 touches
1 conflict

0x9dc696c5…10af

0x065c9d…c394

4 touches
1 conflict

0x3d9051ab…bc3f

0x065c9d…c394

3 touches
1 conflict

0xc1ad6589…ea02

0x065c9d…c394

3 touches
1 conflict

0x583259bf…71bb

0x065c9d…c394

3 touches
1 conflict

0x2528b8f7…21f9

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity