← previous blocknext block →recent activity

Analyzing

Block #73,373,957

23 transactions · 19 stateful · 2026-05-09 03:12:36 UTC

Parallelism

52/100

Blocked

53%

Avg conflicts / tx

1.74

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,373,957  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x14f04193…06ff

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xd53220ed…473a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

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

36 conflicts on slot 0x14f0419303…3406ff

← previous block·next block →recent activity