Block #71,448,628

← previous blocknext block →recent activity

Analyzing

Block #71,448,628

13 transactions · 12 stateful · 2026-04-30 05:20:51 UTC

Parallelism

46/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,448,628  ·  13 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x451e482b…7e7d

0x34b655…2a6f

8 touches
6 conflicts

0x38c47502…1005

0x34b655…2a6f

8 touches
6 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

6 touches
3 conflicts

0xa63b81cd…68c4

0x34b655…2a6f

6 touches
3 conflicts

0xd32f8498…be67

0x34b655…2a6f

6 touches
3 conflicts

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 0xac2a02739b…81721b

← previous block·next block →recent activity