← previous blocknext block →recent activity

Analyzing

Block #72,317,226

7 transactions · 6 stateful · 2026-05-04 05:55:42 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,317,226  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7289c873…f40e

0xd32edf…ff58

5 touches
3 conflicts

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0x7fddda78…e0f1

0xa6afd3…d132

3 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0019

0x1b6862…e19c

2 touches
0 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

2 touches
0 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

3 conflicts on slot 0x7289c8736c…baf40e

← previous block·next block →recent activity