Block #71,284,333

← previous blocknext block →recent activity

Analyzing

Block #71,284,333

10 transactions · 8 stateful · 2026-04-29 11:05:44 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,284,333  ·  10 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

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x09799521…d20c

0x065c9d…c394

2 touches
0 conflicts

0x313a42cf…17d3

0x065c9d…c394

2 touches
0 conflicts

0x3db33c71…c5f4

0x065c9d…c394

2 touches
0 conflicts

0x6a14a18d…6a59

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 0xac206e4761…ffef7d

← previous block·next block →recent activity