← previous blocknext block →recent activity

Analyzing

Block #73,926,151

19 transactions · 16 stateful · 2026-05-11 16:43:54 UTC

Parallelism

63/100

Blocked

69%

Avg conflicts / tx

1.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,926,151  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca103984…0709

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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

21 conflicts on slot 0xca10398442…450709

← previous block·next block →recent activity