← previous blocknext block →recent activity

Analyzing

Block #73,438,033

9 transactions · 7 stateful · 2026-05-09 10:18:58 UTC

Parallelism

33/100

Blocked

71%

Avg conflicts / tx

1.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,438,033  ·  9 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x38d51846…fd92

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x82aa92d9…e3f3

0x065c9d…c394

2 touches
0 conflicts

0xb1ef2a85…9723

0x065c9d…c394

2 touches
0 conflicts

0x45fd2360…df0e

0x065c9d…c394

2 touches
0 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: 0x2a68ba18…8e90c5

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity