← previous blocknext block →recent activity

Analyzing

Block #72,979,399

17 transactions · 13 stateful · 2026-05-07 07:27:24 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,979,399  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x5fd4d3ae…850e

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x37d49489…9309

0x34b655…2a6f

4 touches
1 conflict

0x38f431b8…c65d

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity