← previous blocknext block →recent activity

Analyzing

Block #73,499,946

34 transactions · 22 stateful · 2026-05-09 17:11:01 UTC

Parallelism

82/100

Blocked

59%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,499,946  ·  34 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xe429e4c9…9510

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xddf0e471…ce9d

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity