Block #71,557,532

← previous blocknext block →recent activity

Analyzing

Block #71,557,532

40 transactions · 33 stateful · 2026-04-30 17:30:04 UTC

Parallelism

75/100

Blocked

58%

Avg conflicts / tx

1.8

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,557,532  ·  40 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xb40fd287…c052

0xd32edf…ff58

9 touches
10 conflicts

0x0a6cb118…4ca5

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity