← previous blocknext block →recent activity

Analyzing

Block #73,261,504

44 transactions · 32 stateful · 2026-05-08 14:44:21 UTC

Parallelism

77/100

Blocked

72%

Avg conflicts / tx

1.66

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,261,504  ·  44 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x47fb7cd0…828e

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

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

36 conflicts on slot 0x47fb7cd0f7…34828e

← previous block·next block →recent activity