Block #71,042,403

← previous blocknext block →recent activity

Analyzing

Block #71,042,403

9 transactions · 8 stateful · 2026-04-28 08:15:07 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,042,403  ·  9 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

0x89c4b4d5…1ccb

0x065c9d…c394

4 touches
1 conflict

0x9ba43a03…c3af

0x065c9d…c394

4 touches
1 conflict

0xc7538c53…35d6

0x065c9d…c394

4 touches
1 conflict

0xd7df753c…ce2e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

2 touches
0 conflicts

0x85a88798…f85e

0x34b655…2a6f

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: 0x065c9d28…a9c394

1 conflict on slot 0x89c4b4d50d…f31ccb

← previous block·next block →recent activity