Block #71,704,053

← previous blocknext block →recent activity

Analyzing

Block #71,704,053

14 transactions · 11 stateful · 2026-05-01 09:45:19 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,704,053  ·  14 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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x66a083b4…a17a

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: 0x34b6552d…112a6f

1 conflict on slot 0x1b5d2e607a…9999b5

← previous block·next block →recent activity