← previous blocknext block →recent activity

Analyzing

Block #73,482,987

24 transactions · 18 stateful · 2026-05-09 15:18:06 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,482,987  ·  24 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

0x619de240…bcd7

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0028

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0018

0x1b6862…e19c

12 touches
15 conflicts

0xa87df366…081d

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 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

21 conflicts on slot 0x619de2401b…85bcd7

← previous block·next block →recent activity