Block #71,746,623

← previous blocknext block →recent activity

Analyzing

Block #71,746,623

14 transactions · 10 stateful · 2026-05-01 14:28:54 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,746,623  ·  14 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xff6b5651…df5e

0x065c9d…c394

3 touches
1 conflict

0x1f5073ee…7a57

0x065c9d…c394

3 touches
1 conflict

0xc485929a…4c53

0x065c9d…c394

3 touches
1 conflict

0xb207cdff…b880

0x065c9d…c394

3 touches
1 conflict

0xd74d5bed…5e7e

0x2a68ba…90c5

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity