← previous blocknext block →recent activity

Analyzing

Block #72,314,318

29 transactions · 20 stateful · 2026-05-04 05:36:20 UTC

Parallelism

69/100

Blocked

60%

Avg conflicts / tx

1.52

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,314,318  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x4a4a54f1…f4db

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xf35dca9e…bd89

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

36 conflicts on slot 0x4a4a54f1d8…6bf4db

← previous block·next block →recent activity