← previous blocknext block →recent activity

Analyzing

Block #73,476,223

18 transactions · 17 stateful · 2026-05-09 14:33:08 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,476,223  ·  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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x098d3ea6…1f27

0xd32edf…ff58

9 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity