← previous blocknext block →recent activity

Analyzing

Block #73,602,001

16 transactions · 15 stateful · 2026-05-10 04:29:16 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,602,001  ·  16 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

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0xd8238cd1…dfa0

0x065c9d…c394

4 touches
1 conflict

0xf9f964c0…9e65

0x065c9d…c394

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

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