← previous blocknext block →recent activity

Analyzing

Block #73,490,506

15 transactions · 13 stateful · 2026-05-09 16:08:15 UTC

Parallelism

67/100

Blocked

46%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,490,506  ·  15 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x7baad193…6a15

0xd32edf…ff58

7 touches
6 conflicts

0xd53220ed…4734

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x7d160eac…cf13

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0015

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: 0x754704bc…afb603

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity