Block #71,742,564

← previous blocknext block →recent activity

Analyzing

Block #71,742,564

25 transactions · 22 stateful · 2026-05-01 14:01:49 UTC

Parallelism

92/100

Blocked

5%

Avg conflicts / tx

0.04

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,742,564  ·  25 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

0x936fdcd7…a0c1

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x34180922…5dc1

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xca8faa22…85c1

0x065c9d…c394

3 touches
1 conflict

0x2f097c99…c0c6

0x065c9d…c394

3 touches
1 conflict

0x30f2ce9d…30f2

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 0x936fdcd740…a4a0c1

← previous block·next block →recent activity