← previous blocknext block →recent activity

Analyzing

Block #73,446,619

32 transactions · 25 stateful · 2026-05-09 11:16:09 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,446,619  ·  32 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

0xe136a43e…b61d

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x45364cf9…65d8

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 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 0xe136a43ee8…beb61d

← previous block·next block →recent activity