← previous blocknext block →recent activity

Analyzing

Block #73,050,693

45 transactions · 28 stateful · 2026-05-07 15:22:01 UTC

Parallelism

80/100

Blocked

64%

Avg conflicts / tx

1.04

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,050,693  ·  45 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xa673faa7…37c4

0xd32edf…ff58

11 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3b3a5945…10d0

0x34b655…2a6f

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: 0xd32edf66…9fff58

15 conflicts on slot 0xa673faa7ab…4e37c4

← previous block·next block →recent activity