Block #72,284,400

← previous blocknext block →recent activity

Analyzing

Block #72,284,400

19 transactions · 16 stateful · 2026-05-04 02:16:22 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,284,400  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0de7749d…5bef

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6a53b1c0…c3f2

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity