Block #71,037,243

← previous blocknext block →recent activity

Analyzing

Block #71,037,243

9 transactions · 8 stateful · 2026-04-28 07:40:47 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,037,243  ·  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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x26a58d61…a078

0x34b655…2a6f

4 touches
1 conflict

0x319ab432…90a4

0x34b655…2a6f

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xc613436a…63cd

0x34b655…2a6f

4 touches
1 conflict

0xcbd23469…a4df

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

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