← previous blocknext block →recent activity

Analyzing

Block #72,284,239

28 transactions · 22 stateful · 2026-05-04 02:15:18 UTC

Parallelism

79/100

Blocked

64%

Avg conflicts / tx

1.18

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,284,239  ·  28 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

0x265d1267…ada4

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0028

0x1b6862…e19c

10 touches
10 conflicts

0x1da7723c…80a7

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

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

15 conflicts on slot 0x265d1267cf…3fada4

← previous block·next block →recent activity