Block #71,627,269

← previous blocknext block →recent activity

Analyzing

Block #71,627,269

23 transactions · 17 stateful · 2026-05-01 01:14:15 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,627,269  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd57999cf…d4b5

0xd32edf…ff58

13 touches
21 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x3a3097d7…2ab5

0x1b6862…e19c

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

21 conflicts on slot 0xd57999cf61…0dd4b5

← previous block·next block →recent activity