Block #71,449,860

← previous blocknext block →recent activity

Analyzing

Block #71,449,860

14 transactions · 13 stateful · 2026-04-30 05:29:03 UTC

Parallelism

64/100

Blocked

46%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,449,860  ·  14 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0xfac43f12…b842

0x34b655…2a6f

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x1630ed91…9774

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

0x34b655…2a6f

4 touches
1 conflict

0x5caf9f43…a348

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity