Block #71,742,452

← previous blocknext block →recent activity

Analyzing

Block #71,742,452

16 transactions · 14 stateful · 2026-05-01 14:01:04 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,742,452  ·  16 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x4fdd903c…8406

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x2a51b420…a5e7

0x065c9d…c394

3 touches
1 conflict

0x2b6043a3…23fa

0x065c9d…c394

3 touches
1 conflict

0x342b304b…80a3

0x065c9d…c394

3 touches
1 conflict

0xf0d602fe…e634

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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