Block #71,683,642

← previous blocknext block →recent activity

Analyzing

Block #71,683,642

9 transactions · 7 stateful · 2026-05-01 07:29:27 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,683,642  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x9b225a57…75d5

0x065c9d…c394

4 touches
1 conflict

0xaf98ee75…69e1

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x90b86c38…2b24

0x065c9d…c394

3 touches
1 conflict

0x4d03d7da…88c5

0x065c9d…c394

3 touches
1 conflict

0x22087c40…8e26

0x065c9d…c394

3 touches
1 conflict

0x05c8f6bc…4254

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