Block #72,859,893

← previous blocknext block →recent activity

Analyzing

Block #72,859,893

22 transactions · 18 stateful · 2026-05-06 18:12:01 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,859,893  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x1a1b6854…30df

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity