← previous blocknext block →recent activity

Analyzing

Block #73,014,049

29 transactions · 24 stateful · 2026-05-07 11:18:03 UTC

Parallelism

83/100

Blocked

46%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,014,049  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7f0c5fae…456d

0xd32edf…ff58

9 touches
10 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0002

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0012

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

10 conflicts on slot 0x7f0c5faec5…49456d

← previous block·next block →recent activity