← previous blocknext block →recent activity

Analyzing

Block #72,283,009

25 transactions · 19 stateful · 2026-05-04 02:07:01 UTC

Parallelism

76/100

Blocked

26%

Avg conflicts / tx

0.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,283,009  ·  25 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

0xf0a7ca33…3c7e

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0xaa3492db…3703

0x34b655…2a6f

4 touches
1 conflict

0xaef9058e…322a

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

6 conflicts on slot 0xf0a7ca3337…9d3c7e

← previous block·next block →recent activity