Block #71,683,639

← previous blocknext block →recent activity

Analyzing

Block #71,683,639

7 transactions · 5 stateful · 2026-05-01 07:29:25 UTC

Parallelism

57/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,683,639  ·  7 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xa1c5a7a3…3269

0x065c9d…c394

3 touches
1 conflict

0xa303bbd3…71ad

0xd32edf…ff58

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1eee85ba…6feb

0x065c9d…c394

2 touches
0 conflicts

0x5aa25a63…dbd7

0x065c9d…c394

2 touches
0 conflicts

0x9b225a57…75d5

0x065c9d…c394

2 touches
0 conflicts

0xaf98ee75…69e1

0x065c9d…c394

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity