← previous blocknext block →recent activity

Analyzing

Block #73,328,503

18 transactions · 16 stateful · 2026-05-08 22:10:19 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,328,503  ·  18 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

0x9e266a79…1b08

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

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

21 conflicts on slot 0x9e266a793e…541b08

← previous block·next block →recent activity