← previous blocknext block →recent activity

Analyzing

Block #73,223,735

34 transactions · 26 stateful · 2026-05-08 10:33:17 UTC

Parallelism

85/100

Blocked

58%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,223,735  ·  34 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0002

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…002b

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity