← previous blocknext block →recent activity

Analyzing

Block #72,295,971

17 transactions · 17 stateful · 2026-05-04 03:34:07 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.35

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,295,971  ·  17 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

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

12 touches
15 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

12 touches
15 conflicts

0x9be2b99a…a959

0x34b655…2a6f

12 touches
15 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

12 touches
15 conflicts

0xa7c45762…dc01

0x34b655…2a6f

12 touches
15 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

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: 0xc8689a47…62ee79

15 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity