Block #71,627,283

← previous blocknext block →recent activity

Analyzing

Block #71,627,283

22 transactions · 18 stateful · 2026-05-01 01:14:20 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,627,283  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd1e75e5d…ce32

0xd32edf…ff58

11 touches
15 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0xd77e90ec…8c04

0x3bd359…433a

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0003

0x5afd3e…7620

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x00000000…0005

0x5afd3e…7620

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: 0xd32edf66…9fff58

15 conflicts on slot 0xd1e75e5d9e…f7ce32

← previous block·next block →recent activity