Block #71,742,655

← previous blocknext block →recent activity

Analyzing

Block #71,742,655

32 transactions · 18 stateful · 2026-05-01 14:02:25 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.41

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,742,655  ·  32 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0003

0xe5a8f8…d7a8

10 touches
10 conflicts

0xbc467e7a…af36

0x21e325…7777

10 touches
10 conflicts

0xae3fbd28…a18c

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0xe5a8f8…d7a8

10 touches
10 conflicts

0x00000000…0001

0xe5a8f8…d7a8

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x37699b20…1074

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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: 0xe5a8f88c…7dd7a8

10 conflicts on slot 0x0000000000…000003

← previous block·next block →recent activity