← previous blocknext block →recent activity

Analyzing

Block #73,748,873

25 transactions · 21 stateful · 2026-05-10 20:58:18 UTC

Parallelism

80/100

Blocked

62%

Avg conflicts / tx

1.08

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,748,873  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xcb45d9d6…cb85

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001d

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x3179a6c4…1dd9

0xd32edf…ff58

9 touches
10 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0xc9e97522…3519

0x2a68ba…90c5

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

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: 0x1b68626d…2de19c

10 conflicts on slot 0xcb45d9d62a…b1cb85

← previous block·next block →recent activity