← previous blocknext block →recent activity

Analyzing

Block #73,639,251

35 transactions · 26 stateful · 2026-05-10 08:38:49 UTC

Parallelism

66/100

Blocked

58%

Avg conflicts / tx

2.03

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,639,251  ·  35 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x9d1be47c…e941

0xd32edf…ff58

23 touches
66 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x64461c10…e86d

0x34b655…2a6f

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

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

66 conflicts on slot 0x9d1be47c82…afe941

← previous block·next block →recent activity