Block #72,213,461

← previous blocknext block →recent activity

Analyzing

Block #72,213,461

13 transactions · 12 stateful · 2026-05-03 18:19:41 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.15

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,213,461  ·  13 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

0x629480fc…7d2f

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x77905798…fe3d

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

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 0x629480fc35…277d2f

← previous block·next block →recent activity