← previous blocknext block →recent activity

Analyzing

Block #72,284,225

21 transactions · 17 stateful · 2026-05-04 02:15:12 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.19

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,284,225  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0x06ba1119…3d0f

0xd32edf…ff58

9 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 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: 0x1b68626d…2de19c

10 conflicts on slot 0x0000000000…000012

← previous block·next block →recent activity