← previous blocknext block →recent activity

Analyzing

Block #73,043,106

37 transactions · 25 stateful · 2026-05-07 14:31:26 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,043,106  ·  37 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

0x051b77ff…6f2e

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xd996735f…8735

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

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

21 conflicts on slot 0x051b77ff3c…cf6f2e

← previous block·next block →recent activity