← previous blocknext block →recent activity

Analyzing

Block #73,391,218

13 transactions · 11 stateful · 2026-05-09 05:07:24 UTC

Parallelism

54/100

Blocked

55%

Avg conflicts / tx

1.31

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,391,218  ·  13 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

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0x4c301f24…54c5

0xd32edf…ff58

9 touches
10 conflicts

0x9a555477…19a8

0x754704…b603

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0002

0x63e48b…53f2

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

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

10 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity