← previous blocknext block →recent activity

Analyzing

Block #73,503,921

16 transactions · 13 stateful · 2026-05-09 17:37:34 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,503,921  ·  16 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

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0xa5de1a8b…23ff

0x065c9d…c394

8 touches
6 conflicts

0x9ac040c1…821f

0x1b6862…e19c

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x0747b69c…3895

0xd32edf…ff58

7 touches
6 conflicts

0xd9f18d9a…141d

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity