← previous blocknext block →recent activity

Analyzing

Block #73,917,447

30 transactions · 22 stateful · 2026-05-11 15:45:57 UTC

Parallelism

73/100

Blocked

55%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,917,447  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb2895415…f951

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x1a7e478a…37a5

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xa15427f6…d932

0x34b655…2a6f

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

15 conflicts on slot 0xb289541568…18f951

← previous block·next block →recent activity