← previous blocknext block →recent activity

Analyzing

Block #72,498,698

40 transactions · 28 stateful · 2026-05-05 02:04:36 UTC

Parallelism

80/100

Blocked

54%

Avg conflicts / tx

1.1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,498,698  ·  40 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x036f35c7…f4ff

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0xba5743c7…21c3

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…002c

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 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

28 conflicts on slot 0x036f35c751…28f4ff

← previous block·next block →recent activity