← previous blocknext block →recent activity

Analyzing

Block #71,450,063

37 transactions · 33 stateful · 2026-04-30 05:30:25 UTC

Parallelism

73/100

Blocked

64%

Avg conflicts / tx

2.22

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,450,063  ·  37 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

0x17606ba6…1b6e

0x754704…b603

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x1c913164…5c2e

0x34b655…2a6f

10 touches
10 conflicts

0x21141d8e…3247

0xd32edf…ff58

9 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xe75ce681…ba60

0x188d58…ea8e

8 touches
6 conflicts

0xa4e5d7a6…ca33

0x34b655…2a6f

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: 0x754704bc…afb603

28 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity