← previous blocknext block →recent activity

Analyzing

Block #73,922,284

38 transactions · 30 stateful · 2026-05-11 16:18:09 UTC

Parallelism

84/100

Blocked

53%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,922,284  ·  38 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xcb45d9d6…cb81

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

10 touches
10 conflicts

0xd64852e6…1134

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

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: 0x1b68626d…2de19c

10 conflicts on slot 0xcb45d9d62a…b1cb81

← previous block·next block →recent activity