← previous blocknext block →recent activity

Analyzing

Block #73,353,359

30 transactions · 27 stateful · 2026-05-09 00:55:41 UTC

Parallelism

83/100

Blocked

59%

Avg conflicts / tx

1.37

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,353,359  ·  30 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

0xafd59af5…5257

0xc8689a…ee79

10 touches
10 conflicts

0x2484cc15…5afc

0x34b655…2a6f

10 touches
10 conflicts

0x318ac0bb…6b9c

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

10 touches
10 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0x0f9b918b…212d

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 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: 0xc8689a47…62ee79

10 conflicts on slot 0xafd59af545…b35257

← previous block·next block →recent activity