← previous blocknext block →recent activity

Analyzing

Block #73,503,268

44 transactions · 22 stateful · 2026-05-09 17:33:12 UTC

Parallelism

73/100

Blocked

73%

Avg conflicts / tx

1.66

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,503,268  ·  44 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

0x1aa2bbe5…117d

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x33018431…8f5d

0x188d58…ea8e

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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 0x1aa2bbe566…eb117d

← previous block·next block →recent activity