Block #71,742,274

← previous blocknext block →recent activity

Analyzing

Block #71,742,274

13 transactions · 10 stateful · 2026-05-01 13:59:53 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,742,274  ·  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

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf83a0e2c…a779

0x065c9d…c394

4 touches
1 conflict

0xfe0f2eb4…1b53

0x065c9d…c394

4 touches
1 conflict

0x4ee6f153…3ef4

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

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 0xfefb01895a…9bf726

← previous block·next block →recent activity