Block #71,422,647

← previous blocknext block →recent activity

Analyzing

Block #71,422,647

37 transactions · 24 stateful · 2026-04-30 02:27:43 UTC

Parallelism

78/100

Blocked

54%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,422,647  ·  37 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf8e945d9…61a0

0xd32edf…ff58

15 touches
28 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x269685bf…71ed

0x065c9d…c394

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

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

28 conflicts on slot 0xf8e945d9a9…3261a0

← previous block·next block →recent activity