Block #72,172,216

← previous blocknext block →recent activity

Analyzing

Block #72,172,216

23 transactions · 19 stateful · 2026-05-03 13:42:32 UTC

Parallelism

52/100

Blocked

68%

Avg conflicts / tx

1.78

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,172,216  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x1da1c6cb…bb3f

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

8 touches
6 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity