Block #71,037,423

← previous blocknext block →recent activity

Analyzing

Block #71,037,423

13 transactions · 12 stateful · 2026-04-28 07:41:58 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,037,423  ·  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

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0002

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0003

0x116e7d…d8f1

2 touches
0 conflicts

0x005fb969…2d97

0x34b655…2a6f

2 touches
0 conflicts

0x3702b140…97ea

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

1 conflict on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity