← previous blocknext block →recent activity

Analyzing

Block #73,383,390

24 transactions · 20 stateful · 2026-05-09 04:15:18 UTC

Parallelism

54/100

Blocked

65%

Avg conflicts / tx

2.33

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,383,390  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x971ed8c4…dc45

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

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

45 conflicts on slot 0x971ed8c496…33dc45

← previous block·next block →recent activity