← previous blocknext block →recent activity

Analyzing

Block #73,978,888

35 transactions · 27 stateful · 2026-05-11 22:35:15 UTC

Parallelism

77/100

Blocked

63%

Avg conflicts / tx

1.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,978,888  ·  35 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

0x3d6ba53b…38b4

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x75e73565…45f6

0x1b6862…e19c

8 touches
6 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

0xa15427f6…d932

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0x3d6ba53b34…dc38b4

← previous block·next block →recent activity