Block #71,284,403

← previous blocknext block →recent activity

Analyzing

Block #71,284,403

13 transactions · 11 stateful · 2026-04-29 11:06:12 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,284,403  ·  13 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

0x1627b708…d040

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4201ebd0…a552

0x065c9d…c394

3 touches
1 conflict

0x5e1896f3…1c7d

0x065c9d…c394

2 touches
0 conflicts

0x7fa9c0ca…18bc

0x065c9d…c394

2 touches
0 conflicts

0xb2a1c1b2…e9a0

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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 0x1627b708d5…f6d040

← previous block·next block →recent activity