Block #71,683,503

← previous blocknext block →recent activity

Analyzing

Block #71,683,503

7 transactions · 6 stateful · 2026-05-01 07:28:31 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xccb504f0…dab9

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfade7f5f…7461

0x065c9d…c394

3 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x342c36dd…9c9e

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xb4b5ca86…bc60

0x065c9d…c394

2 touches
0 conflicts

0xde9957dd…e173

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

1 conflict on slot 0xccb504f068…afdab9

← previous block·next block →recent activity