Block #73,214,777

← previous blocknext block →recent activity

Analyzing

Block #73,214,777

22 transactions · 17 stateful · 2026-05-08 09:33:35 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,214,777  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x446bd538…42a9

0x34b655…2a6f

6 touches
3 conflicts

0x4582e32d…1abe

0x34b655…2a6f

6 touches
3 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

6 touches
3 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity