Block #71,688,567

← previous blocknext block →recent activity

Analyzing

Block #71,688,567

8 transactions · 8 stateful · 2026-05-01 08:02:11 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,688,567  ·  8 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

0xbfd366c6…fd71

0x065c9d…c394

4 touches
1 conflict

0x59658b83…2229

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xb9588561…4460

0xd32edf…ff58

3 touches
1 conflict

0x7c63089d…1aa0

0x065c9d…c394

3 touches
1 conflict

0xce7e94b5…5c87

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 0xbfd366c6a2…05fd71

← previous block·next block →recent activity