Block #72,979,621

← previous blocknext block →recent activity

Analyzing

Block #72,979,621

37 transactions · 29 stateful · 2026-05-07 07:28:53 UTC

Parallelism

60/100

Blocked

66%

Avg conflicts / tx

2

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #72,979,621  ·  37 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0x0667759e…336f

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 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

45 conflicts on slot 0x0667759e7e…25336f

← previous block·next block →recent activity