← previous blocknext block →recent activity

Analyzing

Block #73,263,452

32 transactions · 24 stateful · 2026-05-08 14:57:19 UTC

Parallelism

66/100

Blocked

63%

Avg conflicts / tx

2.03

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,263,452  ·  32 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x578edbdb…02e1

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…001c

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…002c

0x1b6862…e19c

16 touches
28 conflicts

0x0f94ee4c…189b

0x1b6862…e19c

16 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

16 touches
28 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

55 conflicts on slot 0x578edbdb0d…5902e1

← previous block·next block →recent activity