← previous blocknext block →recent activity

Analyzing

Block #73,372,889

27 transactions · 22 stateful · 2026-05-09 03:05:30 UTC

Parallelism

70/100

Blocked

59%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,372,889  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x5cafedd4…478a

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

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 0x5cafedd458…9f478a

← previous block·next block →recent activity