← previous blocknext block →recent activity

Analyzing

Block #73,502,308

16 transactions · 13 stateful · 2026-05-09 17:26:47 UTC

Parallelism

56/100

Blocked

54%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,502,308  ·  16 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

10 touches
10 conflicts

0xa9e225f0…f74f

0xd32edf…ff58

9 touches
10 conflicts

0xb6d6d740…e91a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

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: 0x754704bc…afb603

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity