Block #72,283,317

← previous blocknext block →recent activity

Analyzing

Block #72,283,317

45 transactions · 37 stateful · 2026-05-04 02:09:06 UTC

Parallelism

71/100

Blocked

81%

Avg conflicts / tx

2.71

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #72,283,317  ·  45 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xd25f7a9b…3b6b

0xd32edf…ff58

21 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0018

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0028

0x1b6862…e19c

12 touches
15 conflicts

0x91220b8f…7a01

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 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: 0xd32edf66…9fff58

55 conflicts on slot 0xd25f7a9bd3…803b6b

← previous block·next block →recent activity