← previous blocknext block →recent activity

Analyzing

Block #73,373,887

14 transactions · 12 stateful · 2026-05-09 03:12:09 UTC

Parallelism

50/100

Blocked

58%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,373,887  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7c9a55fb…63da

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0x2ce2d49e…d18b

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x7c9a55fb24…c363da

← previous block·next block →recent activity