Block #71,446,191

← previous blocknext block →recent activity

Analyzing

Block #71,446,191

30 transactions · 24 stateful · 2026-04-30 05:04:36 UTC

Parallelism

63/100

Blocked

83%

Avg conflicts / tx

1.93

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,446,191  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x5f77d607…2c84

0x065c9d…c394

10 touches
13 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x451e482b…7e7d

0x34b655…2a6f

10 touches
10 conflicts

0xabd8f0b6…d9d0

0xd32edf…ff58

9 touches
10 conflicts

0x892daf6e…48d8

0x065c9d…c394

8 touches
8 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0xa87df366…0824

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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: 0x065c9d28…a9c394

13 conflicts on slot 0x5f77d60791…b12c84

← previous block·next block →recent activity