← previous blocknext block →recent activity

Analyzing

Block #73,679,599

7 transactions · 6 stateful · 2026-05-10 13:10:57 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,679,599  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xea36a7f5…a8e1

0xd32edf…ff58

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x212fcdb3…8420

0x065c9d…c394

3 touches
1 conflict

0x07271ce5…c9a9

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0xed0fc6f6…9142

0x065c9d…c394

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 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: 0xd32edf66…9fff58

3 conflicts on slot 0xea36a7f56c…54a8e1

← previous block·next block →recent activity